Using GitLab Pipelines
You can build your custom Continuous Deployment jobs using GitLab Pipelines and Bolt APIs.
To use this feature it is required to have a production environment configured in Paradime.
ℹ️ Check our setup guide here based on your data warehouse provider.
Create a CD Bolt schedule
To start create a new Bolt schedule and make sure to add the deferred_schedule
configuration. Depending on your intended behavior you can choose to defer to another production job or defer back to the last CD run.
The deferred_schedule_name
set in the configuration should have at least one successful run available, so that Paradime can pick the manifest.json for state comparison.
Example schedule
Generate API keys and find you workspace token
API keys are generate at a workspace level.
To be able to trigger Bolt using the API, you will first need to generate API keys for your workspace. Got to account settings and generate your API keys, make sure to save in your password manager:
API key
API secret
API Endpoint
Workspace token
You will need this later when setting up the secret in GitLab pipelines.
API KeysCompany & Workspace tokenCreate a GitLab Pipeline
GitLab merged results pipelines is a feature available only on Tier: Premium, Ultimate. Make sure to enable merge results pipelines in GitLab before proceeding to next step.
Now you will need to create a new .gitlab-ci.yml
file at the root of your project your dbt™️ repository. Copy the code block below and enter the values required.
Add the API key and Credential in the GitLab variables
Finally you need to add the API key and credentials generated in the previous step in GitLab CI/CD pipelines.
Set the corresponding values using your credentials for the variable names:
PARADIME_API_KEY
PARADIME_API_SECRET
PARADIME_API_ENDPOINT
Last updated