CircleCI
CircleCI is the world’s largest shared continuous integration and continuous delivery (CI/CD) platform.
In this example, we are going to make use of CircleCI's API to trigger a pipeline automatically on the main branch whenever there is an insert/update/delete on our blog table.
You can use the one-click to deploy on Hasura Cloud to get started quickly
Configuring an Event Transform
You'll need the following environment variables.
CIRCLECI_TOKEN: "<Personal API token https://circleci.com/docs/2.0/managing-api-tokens/>"
CIRCLECI_PIPELINE_URL: "<https://circleci.com/api/v2/project/<PROJECT_SLUG>/pipeline>"
If you are using Docker you can provide these environment variables along with the rest of your Hasura configuration information.
Check out CircleCI API Docs
Importing an Event Transform
Importing actions and events into Hasura apply one or more actions. Actions based on request configurations and will need metadata to be applied. Events need underlying table structure to trigger the events.
Steps required for this integration:
- Metadata Apply
- Migrate Apply
- Metadata Reload
Metadata Apply
To apply metadata into your project. You will need:
- The Hasura CLI installed.
- Run "hasura metadata apply" from the root folder of your Hasura metadata project. In this project, you can find that folder under
/hasura.
More information about Hasura CLI can be found in the documentation.
Migrate Apply
Once metadata is applied, you will apply the database migrations.
hasura migrate apply
Metadata Reload
For the migration changes to reflect, we will execute the metadata reload command.
hasura metadata reload
Submit a new integration
