-
Spike
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
3
-
False
-
-
False
-
-
-
Builds Sprint #22, Builds Sprint #23
-
2
Spike Investigation
- Identify how Shipwright is currently implementing feature gating in the main "build" project.
- Answer the following key questions:
- Do we have mechanisms in shipwright-io/build to enable or disable a feature?
- If a feature can be enabled/disabled at the build controller level, can we similarly disable it in upstream Shipwright operator?
- Which features cannot be disabled by default? Should we be able to disable them?
Approach
TBD
Acceptance Criteria
- Document outlining the status of feature gating in Shipwright
- New feature requests/issues upstream if there are gaps or areas of improvement.
- Identify how we can disable Shipwright features that we consider developer preview, such as the Vulnerability scanning feature.
- is related to
-
BUILD-742 Shipwright Operator Options
-
- New
-
- links to
There are no Sub-Tasks for this issue.