-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
None
-
5
-
False
-
None
-
False
-
-
-
GITOPS Sprint 3247, GITOPS Sprint 3248
Story (Required)
As a developer trying to release GitOps Dynamic Plugin I want to have a flag to toggle static plugin so that it would be possible to backport to old static plugin.
Background (Required)
The reason of this ticket is that OCP will have a release where they leave the static plugin as a fallback.
Slack thread: https://redhat-internal.slack.com/archives/C011BL0FEKZ/p1698853635030619
Related to GITOPS-2369: [DynamicPlugin] Remove static plugin from Console
Out of scope
<Defines what is not included in this story>
Approach (Required)
Set up a flag initialized by the dynamic plugin and disable the static plugin when the flag is set.
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Acceptance Criteria (Mandatory)
Only one of static plugin and dynamic plugin will be displayed in console.
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied
Done Checklist
- Code is completed, reviewed, documented and checked in
- Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
- Continuous Delivery pipeline(s) is able to proceed with new code included
- Customer facing documentation, API docs etc. are produced/updated, reviewed and published
- Acceptance criteria are met
- links to
- mentioned on