FE: Interactive validation in security policy editor

Why are we doing this work

Troubleshooting invalid security policies is currently somewhat difficult. I would be much easier if we could have interactive validation with in-line error reporting like we have on the CI / CD Editor:

We should be able to re-use its implementation with the security orchestration policy schema

Relevant links

Non-functional requirements

• Documentation:
• Feature flag:
• Performance:
• Testing:

Implementation plan

Possible implementation references:

• https://gitlab.com/gitlab-org/gitlab/-/blob/1e7a2d16b7b67fde966aa3ca0cb510a97dd52a5b/app/assets/javascripts/editor/extensions/source_editor_ci_schema_ext.js#L5
• https://gitlab.com/gitlab-org/gitlab/-/blob/1e7a2d16b7b67fde966aa3ca0cb510a97dd52a5b/app/assets/javascripts/pipeline_editor/components/editor/text_editor.vue#L18

Implementation

• frontend Download the schema from the new fetch_schema_service when the page is loaded in the scan_execution_policy_editor
• frontend pass the schema into policy_editor_layout on a newly created schema prop to the policy-yaml-editor
• frontend update policy_yaml_editor to register the schema with the source_editor instance

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.