Create reusable component for security polices popovers
Why are we doing this work
Security orchestration has similar components with tooltip/popover functionality
ee/app/assets/javascripts/security_orchestration/components/policy_editor/scan_execution/action/custom_section_tooltip.vue
ee/app/assets/javascripts/security_orchestration/components/policy_editor/scope/compliance_framework_tooltip.vue
ee/app/assets/javascripts/security_orchestration/components/policy_editor/scan_execution/action/scan_filters/runner_tags_list.vue
It can potentially be refactored to reusable component
Relevant links
Based on comment
Non-functional requirements
-
Documentation: -
Feature flag: -
Performance: -
Testing:
Implementation plan
- Create reusable component
- Replace components from description above with newly created
- Add test coverage
Verification steps
Feature.enable(:compliance_pipeline_in_policies)
Feature.enable(:security_policies_policy_scope)
Make sure popovers work as expected same as before: (Secure -> Policies -> New policy)
- In policy scope section for both scan
result
and scanexecution
policy - New yaml code action for scan
execution
policy - Settings for scan
result
policy
Edited by Artur Fedorov