### Problem to solve [Pipeline execution policies](https://docs.gitlab.com/ee/user/application_security/policies/#scan-execution-policy-schema) are adding support for [compliance framework pipelines](https://docs.gitlab.com/ee/user/project/settings/index.html#compliance-pipeline-configuration) to provide users need a single solution for enforcing jobs to be run as part of a project pipeline. Follow along with progress in this epic https://gitlab.com/groups/gitlab-org/-/epics/7312+ In https://gitlab.com/groups/gitlab-org/-/epics/12324+ we are adding banners to support users to migrate their compliance pipelines over to pipeline execution policies. But this does not deter users from adding new compliance pipelines ### Proposal - Phase 1: Move pipeline UI to accordion when no pipeline set - Phase 1: When saving a framework and pipeline is set, show popup that compliance pipelines are deprecated - Phase 2: Remove pipeline editing from UI when no pipeline set, but leave in API