CI/CD
Dinghy is designed to integrate seamlessly into Continuous Integration and Continuous Delivery (CI/CD) workflows.
Github Action
To easily set up the Dinghy CLI in your GitHub Actions workflows, use the dinghydev/install-dinghy-cli action.
If your .dinghyrc file defines a DINGHY_ENGINE_VERSION, this action will
automatically install the corresponding Dinghy CLI version to ensure a
consistent runtime environment.
Default Github Action
- uses: dinghydev/install-dinghy-cli@v1
By default, this action installs the Dinghy CLI and prepares the default engine image for use.
For TF Operations Action
- uses: dinghydev/install-dinghy-cli@v1
with:
prepare-images: release,tf
If your job will use tf operations, it's recommended to prepare the image beforehand. This allows you to obtain more accurate timing information for the tf operations themselves.
CI/CD Demo Project
You can view a practical example of a CI/CD pipeline using Dinghy in the dinghydev/dinghy-example-cloudfront-sites demo project.
Avaliable images
- release - the engine image
- tf - for Terraform/OpenTofu operations
- drawio - draw.io image to convert
.drawiofile to.pngfile - site - to render docusaurus.io based site
- awscli - for operations rely on awscli