-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ConfigmapRef does not respect optional and default keyword #8262
Comments
@louisnow: There are no area labels on this issue. Adding a label will help expedite your issue. If you are unsure what to do, make your best guess. We can change it later
DetailsI am a bot created to help the argoproj developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the DeFiCh/oss-governance-bot repository. |
/area templates/resource |
The bug is here: argo-workflows/workflow/common/util.go Line 152 in 78f01f2
It's clear the code does not take this into account. I think that @terrytangyuan might be busy. @louisnow would you like to submit a PR? |
argoproj#8262 Signed-off-by: Yuan Tang <[email protected]>
This should be fixed in #8271. |
#8262 (#8271) Signed-off-by: Yuan Tang <[email protected]>
#8262 (#8271) Signed-off-by: Yuan Tang <[email protected]>
Checklist
Summary
What happened/what you expected to happen?
Optional
anddefault
keywords are not respected when usingconfigMapKeyRef
.Workflow errors while trying to reference a key that does not exist.
What version are you running?
v3.2.9
Emissary Executor
Diagnostics
Paste the smallest workflow that reproduces the bug. We must be able to run the workflow.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: