Disable Compliance pipeline field for Premium licenses
requested to merge 409017-disable-compliance-pipeline-field-in-compliance-frameworks-for-premium-licenses into master
What does this MR do and why?
Disables the compliance pipeline configuration input when adding/editing a compliance framework. This has already been blocked on the backend here Error when trying to add new Compliance Framewo... (#408957 - closed)
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
For premium and below plan
For ultimate plan
How to set up and validate locally
- on a top level namespace with a GitLab Premium subscription follow the steps in Compliance frameworks
- The compliance pipeline configuration input should be disabled (as this is a GitLab Ultimate feature)
- Hover over the field and popover should explain further it is for GitLab Ultimate subscription
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #409017 (closed)
Edited by Nate Rosandich