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
After creating or updating a CR of type Product, the changes are not automatically promoted to staging and production. This means that the changes will not actually take effect. Therefore, using a GitOps approach is impossible with the operator in its current state.
Requested solution: Please add fields in the CR (e.g. "production": true) or options to the Operator that allow to automatically promote any changes to production.
The text was updated successfully, but these errors were encountered:
adding a field in the CR (production: true), does not seem a good idea. The CR represents a state and promoting is kind of action. For example, what if the user turns production to false? There is no straight way to revert changes. 3scale allows, via the configuration history, to apply any past configuration to be applied. However, the binding with an attribute like production: true does not seem right.
Overall, there will be a mechanism using CRs to promote to staging and/or production. A good design is missing, yet, though.
After creating or updating a CR of type Product, the changes are not automatically promoted to staging and production. This means that the changes will not actually take effect. Therefore, using a GitOps approach is impossible with the operator in its current state.
Requested solution: Please add fields in the CR (e.g. "production": true) or options to the Operator that allow to automatically promote any changes to production.
The text was updated successfully, but these errors were encountered: