[Frontend]: Add variables deny/allow selector to pipeline execution policy
Why are we doing this work
As customers work to strike a balance between security/compliance and developer velocity, enforcement of CI jobs within project pipelines is only one dimension. There is also a desire to control the behavior for managing and manipulating variables for jobs in a project enforced by a pipeline execution policy.
Relevant links
Non-functional requirements
-
Documentation: -
Feature flag: security_policies_optional_variables_control -
Performance: -
Testing:
Implementation plan
- Add new component according to design to
ee/app/assets/javascripts/security_orchestration/components/policy_editor/pipeline_execution/action - Variables control for scan_execution policy in
ee/app/assets/javascripts/security_orchestration/components/policy_editor/scan_execution/action/scan_filters/ci_variables_selectors.vuecan be referenced as an example - Add test coverage
- Can be broken down into multiple MR's or Issues
Verification steps
Edited by Artur Fedorov