likvido/Build and deploy via GitOps repo
Will build and deploy the given docker application to the given container registry and update the deployment file in the given GitOps repository
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Apr 10, 2026
- License
- MIT
Pinned Snippet
uses: likvido/action-release@33264215bca4e4a54c5befd928d6ff42f4a71b8e # v3.12tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| docker-working-directory | The path to the working directory | no | . |
| docker-file-relative | The path to the Dockerfile relative to the docker-working-directory | yes | — |
| app-name | The name of the app | yes | — |
| environment | The name of the environment. Typicaly either "staging" or "production" | yes | — |
| kubernetes-namespace | The namespace to deploy to inside the Kubernetes cluster | no | default |
| acr-registry | The name of the ACR registry to upload the image to | yes | — |
| azure-service-principal-id | The ID of the service principal to use when pushing the image | yes | — |
| azure-service-principal-password | The password of the service principal to use when pushing the image | yes | — |
| gitops-repo-url | The URL to the GitOps repo to update | yes | — |
| github-app-id | The ID of the Github app to use for updating the GitOps repo | yes | — |
| github-app-private-key-base64 | The base64 encoded private key of the Github app to use for updating the GitOps repo | yes | — |
| github-app-installation-id | The installation id of the Github app to use for updating the GitOps repo | yes | — |
| gitops-deployment-file | The path to a file in the GitOps repo you want to update | no | — |
| use-registry-cache | Enable registry-based build cache for faster builds | no | false |
Outputs
no outputs