Rename threat_monitoring to security_orchestration
What does this MR do and why?
- with a change in product direction, I renamed all the directories appropriately
How I made this change
- Rename the
ee/app/assets/javascripts/threat_monitoring/
directory toee/app/assets/javascripts/security_orchestration
- Rename the
ee/spec/frontend/threat_monitoring/
directory toee/spec/frontend/security_orchestration
- Global search for
/threat_monitoring/
and replace with/security_orchestration
- Walk through the pages to ensure they still work
- Run all the tests
Screenshots or screen recordings
Page | Before | After |
---|---|---|
Policies Page | ![]() |
No visual change |
Policies Drawer | ![]() |
No visual change |
New Policy Page | ![]() |
No visual change |
Edit Policy Page | ![]() |
No visual change |
Change Security Policy Project | ![]() |
No visual change |
How to set up and validate locally
- Upload a GitLab Ultimate license
- Navigate to a project =>
Security & Compliance
=>Policies
- View the policies, change the security policy project, create a policy, edit a policy
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 #352287 (closed)
Edited by Simon Knox