Spike: Permissions for security_policy_bot to access CI configs for scheduled Pipeline Execution Policies

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Why are we doing this work

In the scope of this Spike, we would like to verify what we should do to support Scheduled Pipeline Execution Policies with the CI configs in private repositories. In Spike: Prepare PoC to introduce scheduled Pipel... (#472671 - closed), we will start with a public CI config to avoid dealing with the access. We want to allow users to use a private repository for the CI configs as well.

As an expected result of this Spike, we would like to get the following:

• PoC MR with proposed changes for backend or initial plan how to implement it
• implementation issues for backend and frontend