You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Observation
There are times where a common codebundle, such as k8s-namespace-health, might want to have a global configuration override for a user. While we could fork this and modify the templates, I suspect it would be useful to have a configuration option inside of workspaceInfo.yaml for this as well.
Possible Suggestions
On a best-effort basis, we could take in some sort of path under the codecollections spec that enumerate the configuration override in a similar format as a kustomization patch.
Any other details or context
This simply makes it easier to apply the config across many instances rather than overriding each single one. We would still support per-slx overrides (which are handled at the RunWhen Platform configuration side). This option is just a way to override for all instances of a codebundle.
The text was updated successfully, but these errors were encountered:
Observation
There are times where a common codebundle, such as k8s-namespace-health, might want to have a global configuration override for a user. While we could fork this and modify the templates, I suspect it would be useful to have a configuration option inside of workspaceInfo.yaml for this as well.
Possible Suggestions
On a best-effort basis, we could take in some sort of path under the
codecollections
spec that enumerate the configuration override in a similar format as a kustomization patch.Any other details or context
This simply makes it easier to apply the config across many instances rather than overriding each single one. We would still support per-slx overrides (which are handled at the RunWhen Platform configuration side). This option is just a way to override for all instances of a codebundle.
The text was updated successfully, but these errors were encountered: