Update save of policy for compliance migration
What does this MR do and why?
Update save of policy for compliance migration
- as part of Move creation of security policy project to bac... (#464329 - closed), I refactored the way policies are saved to DRY the code out. In between that MR getting merged and me starting to turn the feature flag on, [Compliance Pipelines][FE] Policy Editor uses p... (!164423 - merged) was merged, which was not captured in my work. This MR adds the work you did there to the save policy code to ensure the merge request gets the proper title and description
- add url parameters to request in editor wrapper
- update tests
Changelog: changed
EE: true
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Video | Screenshot |
|---|---|
| test_migration_small |  |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
- Upload a GitLab Ultimate license
echo "Feature.enable(:security_policies_project_background_worker)" | rails c- Navigate to a group => Secure => Compliance center
- Create a framework which uses pipeline configuration path
- Save framework, enter editing of this framework
- Click 'Migrate pipeline to a policy'
- Observe prefilled form
- Create merge request
- Observer merge request title and description
Related to #482525 (closed)
Edited by Alexander Turinske