Deprecated definitionFrom in cluster variables #10666
Labels
area/clusterclass
Issues or PRs related to clusterclass
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What would you like to be added (User Story)?
As a user I want a clean and simple API surface
As a CC or Runtime Extensions author I want clear guidelines about variable definition
Detailed Description
Back when we introduced variable discovery for runtime extensions, we discussed a lot about how to handle conflicts in case two entities (either cluster class inline variables or runtime extensions) define a variable with the same name but a different type definition - aka conflicts -.
The solution we came up for was based on the idea of handling this with a "degraded UX", forcing the user to specify the
definitionFrom
value when setting the variable value.After some time and experience with this feature, it seems this is unnecessary complexity; we should simply the user experience, drop
definitionFrom
and leave to the cluster class and Runtime Extensions authors the responsibility to avoid conflict, for two reasons:Anything else you would like to add?
We still think that is valuable to enforce that each entity (either cluster class inline variables or runtime extensions) must define all the variables it is using, because in case one of those will drift, everyone else using the same variable won't have unexpected side effects.
However, also in this case, we should force to the entity owners (cc or runtime extension authors) the resolution of the issue.
Please also note that strategies like naming conventions (eg. use a different prefix for each entity owner) can be stiil be used to avoid conflicts, but finding a shared semantic shuold alway be the preferred way to go for, because it ultimately improve the user experience on all the clusters derived from a cluster class.
Label(s) to be applied
/kind feature
/area clusterclass
/priority important-longterm
/triage accepted
/help
The text was updated successfully, but these errors were encountered: