likvido/Likvido Deployment Pipeline
A composite action to build and deploy your application based on the triggering event and branch.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| staging-branch-name | The name of the staging branch. | yes | — |
| production-branch-name | The name of the production branch. | yes | — |
| pull-request-dockerfile-target | The target for the Dockerfile during pull request builds. | yes | — |
| docker-working-directory | The working directory for Docker. | yes | — |
| dockerfile-relative-path | The relative path to the Dockerfile. | yes | — |
| app-name | The name of the application. | yes | — |
| kubernetes-namespace | The Kubernetes namespace to deploy to. | yes | — |
| azure-service-principal-id | Azure Service Principal ID | yes | — |
| azure-service-principal-password | Azure Service Principal Password | 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 |
| jira-token | Bearer token for the Visma Jira gateway. When provided, every production deploy is reported to Visma ENGP/SDOP via likvido/action-sdop-reporter. Leave empty to skip reporting. | no | "" |
Outputs
no outputs