Prerequisites
- A GitLab account — with permissions to create projects and generate personal access tokens
- A Maverics Console account — with access to create or edit deployments
GitLab Setup
Create a Repository
Create a new GitLab project (or use an existing one) for Maverics configuration storage. This project will hold the signed config bundles published by the Console.
Generate a Personal Access Token
Generate a personal access token for the Console to read and write config bundles to the repository. The token needs
read_repository and write_repository scopes.- In GitLab, click your avatar on the left sidebar, then click Preferences
- On the left sidebar, click Access tokens
- Click Add new token
- Enter a Token name (e.g., “Maverics Console”)
- Set an Expiration date (default is 365 days; GitLab 17.6+ allows up to 400 days)
- In Select scopes, check
read_repositoryandwrite_repository - Click Create personal access token
- Copy the token value from Your new personal access token — paste this into the Console’s Token field
Storage Configuration
Configure these fields in the Console when creating or editing a deployment with the GitLab provider.| Field | Required | Description |
|---|---|---|
| Namespace | Yes | Your GitLab organization name |
| Repository | Yes | The GitLab repository name |
| Branch | Yes | The branch in the repository |
| Token | Yes | A personal access token with read_repository and write_repository scopes |
| Configuration File Path | No | The path within the repository where the bundle is stored |
The Orchestrator uses the corresponding config source type to retrieve bundles from the deployment provider. If the Console deploys to GitLab, the Orchestrator uses the GitLab config source to poll for updates.