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
Define a way for the content author to specify what parameters are user-facing, along with a way to plumb them through from the ClusterExtension spec the templating engine
Example use case: I publish a bundle for my Widget app, and the only knobs I want users to be able to tweak are replica count and logging verbosity.
This either needs to accommodate v0 subscription config settings (e.g. env vars, node selector, etc.), or we need a different mechanism for that.
The text was updated successfully, but these errors were encountered:
In order to keep watch namespace configuration out of the Extension API as a first class field, I think we should define our own schema/values that account for watch namespaces and subscription config, and put that in scope for the initial registry+v1 bundle support in Extension+App
joelanford
changed the title
Extension parameters passed through to App
[epic] Extension parameters passed through to templating engine
Apr 4, 2024
joelanford
changed the title
[epic] Extension parameters passed through to templating engine
[epic] ClusterExtension parameters passed through to templating engine
Apr 4, 2024
Define a way for the content author to specify what parameters are user-facing, along with a way to plumb them through from the ClusterExtension spec the templating engine
Example use case: I publish a bundle for my Widget app, and the only knobs I want users to be able to tweak are replica count and logging verbosity.
This either needs to accommodate v0 subscription config settings (e.g. env vars, node selector, etc.), or we need a different mechanism for that.
The text was updated successfully, but these errors were encountered: