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
Is your feature request related to a problem? Please describe.
ComponentDefinition revisioning is currently auto generated and this poses a problem where the version may not be the same across clusters. When we pin a version to a component instance, it will need to be updated to reflect the ComponentDefinition version in that cluster. This means that the workflow files that the app developers write will have to target each cluster separately which may not be feasible if we have a large number of clusters with different deployment/maintenance windows
Describe the solution you'd like
The ability to use a custom revision with semantic versioning will give the app developer both the scope of changes in the ComponentDefinition as well as to pin to a more synchronized version number. Describe alternatives you've considered
If component revision is not able to be customized, maybe allow a extra revision label which could be referred in the component instance
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
ComponentDefinition revisioning is currently auto generated and this poses a problem where the version may not be the same across clusters. When we pin a version to a component instance, it will need to be updated to reflect the ComponentDefinition version in that cluster. This means that the workflow files that the app developers write will have to target each cluster separately which may not be feasible if we have a large number of clusters with different deployment/maintenance windows
Describe the solution you'd like
The ability to use a custom revision with semantic versioning will give the app developer both the scope of changes in the ComponentDefinition as well as to pin to a more synchronized version number.
Describe alternatives you've considered
If component revision is not able to be customized, maybe allow a extra revision label which could be referred in the component instance
The text was updated successfully, but these errors were encountered: