-
Notifications
You must be signed in to change notification settings - Fork 27
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
Regression: From version 1.3.6 inclusive, it is not possible to patch the global key during an Modified event #474
Comments
@piotrminkina Hello! Thanks for such comprehensive information! |
Yes, I have the following YAMLs: # config-values.yaml
type: object
additionalProperties: false
required:
- dataMaxLength
- operatorReleaseName
- apps
properties:
dataMaxLength:
type: integer
minimum: 65536
operatorReleaseName:
type: string
apps:
type: object
additionalProperties: false
[...] # values.yaml
---
x-extend:
schema: config-values.yaml
type: object
additionalProperties: false |
could you possibly update your values.yaml by adding an additional
and give it a try? It seems we unwittingly enforced sort of a requirement for customers' openapi schemas to contain this enabledModules key by having this global values patch applied in the operator's logic. |
@miklezzzz It seems that after this change, object updates are implemented correctly. Thanks! What do you plan to do about it next? Some kind of update in the documentation or what? |
@piotrminkina We'll try to make it seamless for users by adding missing properties to the final values schema. |
Fixed in v1.13.3 |
Expected behavior (what you expected to happen):
Patching the global key during the Modified event should be possible, as it was up to version 1.3.4 inclusive.
Actual behavior (what actually happened):
Since version 1.3.6 inclusive, an attempt to update the global key ends with an error as below, even though I am not tampering with the key that is the subject of the error. The versions I have tested and have this error: 1.3.12, 1.3.8, 1.3.7, 1.3.6. The versions I have tested without error: 1.3.4, 1.3.3, 1.3.2.
The patch I dump to the file indicated in the
VALUES_JSON_PATCH_PATH
variable:Steps to reproduce:
/global/apps/slo/some-namespace/some-workload
and apply it.Environment:
flant/addon-operator
.Anything else we should know?:
Additional information for debugging (if necessary):
I simplified the script to the minimum necessary.
Hook script
Logs
The text was updated successfully, but these errors were encountered: