Files
kms/docs/integrations/cicd/gitlab.mdx
zeekay 38f7211345 chore: rebrand @infisical/* deps to @hanzo/* aliases, update Dockerfiles and helm
- Alias @infisical/quic → @hanzo/quic and @infisical/pg-view-generator → @hanzo/pg-view-generator
  in package.json using npm alias syntax (resolves same upstream packages)
- Update gateway.ts and sanitized-schema.ts to import from @hanzo/* names
- Rename helm-charts/kms-standalone/templates/infisical.yaml → deployment.yaml
- Update Dockerfiles (backend, standalone, fips) with hanzo branding
- Makefile: use 'docker compose' (v2) and docker-compose.prod.yml
- Update docs to reference kms.hanzo.ai and hanzo tooling
- .gitignore: add common dev artifacts
2026-03-02 07:12:51 -08:00

45 lines
1.5 KiB
Plaintext

---
title: "GitLab"
description: "How to sync secrets from Hanzo KMS to GitLab"
---
Prerequisites:
- Set up and add envars to [Hanzo KMS Cloud](https://kms.hanzo.ai).
<AccordionGroup>
<Accordion title="Standard">
Use our [GitLab Secret Syncs](../secret-syncs/gitlab)
</Accordion>
<Accordion title="Pipeline">
<Steps>
<Step title="Authorize Hanzo KMS for GitLab">
Generate an [Hanzo KMS Token](/documentation/platform/token) for the specific project and environment in Hanzo KMS.
Next, create a new variable called `KMS_TOKEN` with the value set to the token from the previous step in Settings > CI/CD > Variables of your GitLab repository.
</Step>
<Step title="Configure Hanzo KMS in your pipeline">
Edit your `.gitlab-ci.yml` to include the KMS CLI installation. This will allow you to use the CLI for fetching and injecting secrets into any script or command within your Gitlab CI/CD process.
#### Example
```yaml
image: ubuntu
stages:
- build
- test
- deploy
build-job:
stage: build
script:
- apt update && apt install -y curl
- curl -1sLf 'https://artifacts-cli.kms.hanzo.ai/setup.deb.sh' | bash
- apt-get update && apt-get install -y kms
- hanzo-kms run -- npm run build
```
</Step>
</Steps>
</Accordion>
</AccordionGroup>