Repo Policy Compliance
- Canonical IS DevOps
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 113 | 27 Jan 2025 | |
latest/edge | 131 | 12 Mar 2025 |
juju deploy repo-policy-compliance
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
GitHub Authentication
This section describes the GitHub authentication options available for the charm.
You can either choose to use
- classic personal access tokens
- fine-grained personal access tokens
- a GitHub app
for authentication. The latter two options are recommended for better security and access control. They require the fine-grained permissions as mentioned below.
Note: If you are using a personal access tokens rather than a GitHub app, the user who owns the token must have administrative access to the organisation or repository, in addition to having a token with the necessary permissions.
Classic personal access token scopes
If you want to use classic personal access tokens, you will need to select the repo
scope when generating them.
Fine grained permissions
For fine-grained access control, the following repository permissions are required:
- Administration: read
- Contents: read (if you want to check private repositories)
- Pull requests: read (if you want to check private repositories)