likvido/SDOP/ENGP reporter
Reports a production deployment to Visma's ENGP/SDOP Jira gateway (DORA metrics)
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit May 12, 2026
- License
- None
Pinned Snippet
uses: likvido/action-sdop-reporter@9d38151d241739bb0a3edc076697f127e549b95c # v1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| jira-token | Bearer token for the Visma Jira gateway. Generated in Hubble. | yes | — |
| app-name | Service name (e.g. webapp-api). Becomes part of the per-service Jira label. | yes | — |
| repo-name | The GitHub repository in owner/name form (typically the github.repository context value). Used to namespace the per-service label. | yes | — |
| deployment-start | ISO 8601 UTC timestamp captured immediately before the production deploy step. | yes | — |
| deployment-status | Outcome of the production deploy step: success, failure, cancelled, or skipped. | yes | — |
| exclude-from-metrics | If true, the ENGPexclude label is added so Visma ignores the ticket. Default true; flip to false after Visma has reviewed the onboarding. | no | true |
| dry-run | If true, log the payload but do not call the Jira gateway. | no | false |
| github-token | Token used to query the GitHub API for the previous successful run. Defaults to the workflow token. | no | ${{ github.token }} |
| jira-host | Visma Jira gateway host. Override only for testing. | no | https://prod.integration-hub.visma.com |
Outputs
| name | description |
|---|---|
| issue-key | The key of the created Jira issue (empty on dry-run). |
| from-sha | The SHA used as the start of the lead-time range. |