Asynchronously call method
What does this MR do and why?
Asynchronously call method
- the method is async, so it needs to be called that way
- follow up from !164268 (comment 2102080796)
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.
Before | After |
---|---|
No visual change |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
- Upload a GitLab Ultimate license
- Navigate to a new project/group => Secure => Policies => New policy => Pipeline execution project => Create a policy
- Verify the user is navigated to the newly created security policy project with an MR
- Navigate to the new project/group => Secure => Policies => New policy => Pipeline execution project => Create a policy
- Verify the user is navigated to the security policy project with an MR
- Navigate to the new project/group => Secure => Policies => Edit policy project => Remove the linked project
- Navigate to the new project/group => Secure => Policies => New policy => Pipeline execution project => Create a policy
- Verify the error appears and a user can still take actions on the page
- Repeat the steps for every policy type
- Enable the ff
echo "Feature.enable(:security_policies_project_background_worker)" | rails c
- Verify the steps above work for every policy type
Related to #464329 (closed)
Edited by Alexander Turinske