Compliance frameworks: post migration workflow
What does this MR do and why?
How to validate locally
- Enable feature flag
ff_compliance_pipeline_maintenance_mode
in rails console (rails c
):Feature.enable :ff_compliance_pipeline_maintenance_mode
- Visit compliance center Docs
- Create a framework which uses pipeline configuration path
- Save framework, enter editing of this framework
- Observe deprecation warning
- Click 'Migrate pipeline to a policy'
- Observe prefilled form
- Create merge request
- Observer merge request title and description
- Merge this merge request and go back to compliance framework editing page
- Observe that deprecation warning changed text
MR acceptance checklist
Please evaluate this MR against the [MR acceptance checklist] (https://docs.gitlab.com/ee/development/code_review.html#acceptance-checklist). It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Related to #476626 (closed)
Edited by Illya Klymov