Introduction
The Deploy API allows you to deploy your project outside of Holistics, making integrating with CI/CD workflows easier. This integration unlocks the full potential of an “as-code” approach, enhancing automation and scalability. This is useful for scenarios like:
-
Auto deploying the latest update after merging PR into the
masterbranch, by integrating Deploy API with the CICD workflow. -
Auto deploying the latest update after new changes are pushed to
masterbranch.
CICD Workflow Integration
Besides the Deploy API, we also provide a GitHub Action that makes it easy to integrate the deployment with your workflow.
Here is a demo of Auto Deployment with Deploy API and GitHub Action
Example GitHub Action config
name: Deploy AML
on:
push:
branches:
- master
pull_request:
branches:
- master
types:
- closed
jobs:
deploy-aml:
if: github.event.pull_request.merged == true || github.event_name == 'push'
runs-on: ubuntu-latest
env:
HOLISTICS_API_KEY: ${{ secrets.HOLISTICS_API_KEY }}
HOLISTICS_HOST: 'https://secure.holistics.io'
steps:
- name: Checkout repository
uses: actions/checkout@v3
- name: Deploy AML
uses: holistics/[email protected]
We believe this update will enhance your workflow with Holistics. As always, we appreciate your feedback and support!
For more information, please refer to our public doc here: Auto Deployment with Deploy API | Holistics Docs (4.0)
