Skip to content

Rename threat_monitoring to security_orchestration

Alexander Turinske requested to merge 352287-rename-threat-monitoring into master

What does this MR do and why?

  • with a change in product direction, I renamed all the directories appropriately

How I made this change

  1. Rename the ee/app/assets/javascripts/threat_monitoring/ directory to ee/app/assets/javascripts/security_orchestration
  2. Rename the ee/spec/frontend/threat_monitoring/ directory to ee/spec/frontend/security_orchestration
  3. Global search for /threat_monitoring/ and replace with /security_orchestration
  4. Walk through the pages to ensure they still work
  5. Run all the tests

Screenshots or screen recordings

Page Before After
Policies Page Screen_Shot_2022-05-24_at_10.16.53 No visual change
Policies Drawer Screen_Shot_2022-05-24_at_10.28.07 No visual change
New Policy Page Screen_Shot_2022-05-24_at_10.17.25 No visual change
Edit Policy Page Screen_Shot_2022-05-24_at_10.17.54 No visual change
Change Security Policy Project Screen_Shot_2022-05-24_at_10.17.08 No visual change

How to set up and validate locally

  1. Upload a GitLab Ultimate license
  2. Navigate to a project => Security & Compliance => Policies
  3. 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.

Related to #352287 (closed)

Edited by Simon Knox

Merge request reports