Conversation
This field can be used by adopters to pass arbitrary data to the operator. Field is added to all three CRDs for maximum configurability. Bumped version number to `Session.v1beta8`, `Workspace.v1beta5` and `AppDefinition.v1beta10`.
There was a problem hiding this comment.
I think we miss bumping the chart version of the crds.
Besides that I have one question.
The current options field allows to add one object with arbitrary integer or string properties, if I understand this correctly.
Would an array of objects that have a key/id property + allows any further integer and string properties make sense as well?
Then for each customization users could add an options object with a known id of the customization + the required values.
This might be a bit more tidy in the long run rather than having a flat list. But maybe this makes it more complicated in other areas
|
I bumped the chart version. I see your point, but believe that adoptors that need this could simply prefix the keys with a customization string and a If this is nesting is requested a lot we can still think about it. WDYT? |
2 participants
This field can be used by adopters to pass arbitrary data to the operator.
Field is added to all three CRDs for maximum configurability.
Bumped version number to
Session.v1beta8,Workspace.v1beta5andAppDefinition.v1beta10.Main Repo PR: https://github.com/eclipsesource/theia-cloud/pull/293