Automate Cerbos policy deployments with Bitbucket Pipelines
Push validated Cerbos policies to Cerbos Hub on every merge using a Bitbucket Pipeline.
Pipeline-driven
A single YAML file triggers policy uploads on every push to your main branch
Secured variables
Store Cerbos Hub credentials as secured repository variables, injected securely at runtime
Zero-downtime updates
Cerbos Hub distributes updated bundles to connected PDPs with no restarts or redeployments
How Cerbos works with Bitbucket Pipelines
Authorization policies should go through the same review and deployment rigour as application code. Bitbucket Pipelines lets you automate that workflow so every policy change is tested and deployed without manual steps.
Cerbos Hub stores your compiled policy bundles and distributes them to connected PDP instances. A CI/CD pipeline pushes validated policies to Cerbos Hub on every merge, and your PDPs pick up the changes automatically.
With Bitbucket Pipelines handling the pipeline and Cerbos Hub handling distribution, policy updates flow from pull request to production with a full audit trail and zero downtime.
How to deploy Cerbos policies with Bitbucket Pipelines
- Create a pipeline file, Add
bitbucket-pipelines.ymlto your repository with a step that runs the cerbosctl Docker image. - Store credentials as secured variables, Add
CERBOS_HUB_CLIENT_IDandCERBOS_HUB_CLIENT_SECRETas secured repository variables in Bitbucket. - Push to main, Every push to main triggers the pipeline, which uploads your policies to Cerbos Hub using
hub store replace-files. - PDPs update automatically, Connected PDP instances pull the latest policy bundle from Cerbos Hub with zero downtime.
FAQ
How does the Bitbucket pipeline deploy policies?
A pipeline step runs the cerbosctl Docker image and executes `hub store replace-files` to upload your policy directory to Cerbos Hub. Connected PDP instances pull the updated bundle automatically.
What credentials do I need?
You need a Cerbos Hub client ID and client secret with Read & Write permissions, stored as secured repository variables in Bitbucket.
Do I need to enable Pipelines first?
Yes. Bitbucket Pipelines must be enabled for your repository before the pipeline configuration file is picked up.
Learn more about Cerbos
Related integrations
View all integrations →
Cerbos + Bitbucket Pipelines
- Policies deployed to Cerbos Hub automatically on every merge via Bitbucket Pipelines
- Connected PDP instances pick up changes with zero downtime
- Policy changes go through the same review process as application code
- Full audit trail from commit to production deployment