-
Notifications
You must be signed in to change notification settings - Fork 47
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
unable to update arrays via parameterKey #171
Comments
I tracked down the problem. We have seen several issues in last few release of kubevela, and it may be unrelated to workflow.
If I add this information directly to the application CR values: property, then the behavior of kubevela 0.6.5 workflow 0.3.3 is restored. |
Empty arrays get this error as well:
We need more flexibility in how to update arrays. I basically have to populate an array in order to use kubevela and this poses problems since this array needs to be null when kubevela isn't operating on it. |
Can you provide a workflow yaml to reproduce this? |
If you're familiar with cert-manager, it represents solvers in an array:
Here's a workflow to attempt to update it
Arrays are problematic, b/c you can not append to an array. So for me to add to solvers, I get index out of range errors until I provide a default values with 2 items in the array. |
Annotation workflow example:
I'll get invalid yaml (keys cannot have quotes) from this workflow until I populate values.yaml with
|
Describe the bug
When attempting to update an array in values, it's no longer possible to do so. Instead, it creates a map["0"] entry.
To Reproduce
use a parameterKey
myscore[0]
Expected behavior
Instead it produces
Screenshots
Actual
Expected
Additional context
I tracked down this drift from expected array output to the following PRs
After this PR, an oddity is emitted with
[99,...]
instead of[99]
#86Arrays can no longer be updated by workflows, instead get treated as maps
#112
The text was updated successfully, but these errors were encountered: