-
Feature Request
-
Resolution: Done
-
Major
-
2.11.0 GA
-
5
-
False
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Yes
-
+
-
Undefined
-
https://gitlab.cee.redhat.com/red-hat-3scale-documentation/3scale-documentation/-/merge_requests/1114, https://gitlab.cee.redhat.com/red-hat-3scale-documentation/3scale-documentation/-/merge_requests/1120, https://gitlab.cee.redhat.com/red-hat-3scale-documentation/3scale-documentation/-/merge_requests/1121, https://github.com/3scale/3scale-operator/pull/742, https://github.com/3scale/3scale-operator/pull/774, https://github.com/3scale/3scale-operator/pull/773
-
-
MGDAPI - Sprint 24, MGDAPI - Sprint 25, MGDAPI - Sprint 26, API CCS Sprint 32 (3Scale)
When there is a change in Product or in any related object required for proper Product functionality, the change should be promoted to Staging Apicast and/or to Production Apicast configuration. Now the 3scale Operator doesn't do this, so user cannot use the Product after definition in CRDs.
- is duplicated by
-
THREESCALE-7920 Add ability to promote Proxy from staging to production in the Product CR via the Operator application capabilities
- Closed
- links to
- mentioned on