limepoint/opschain change
run an opschain change
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Nov 1, 2023
- License
- None
Pinned Snippet
uses: limepoint/opschain-github-action@a3f7a2828a5d4f34d93c3992aa407e56fe2cff36 # opschain-action-v3tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| opschain_apiBaseUrl | OpsChain API Base URL | yes | — |
| opschain_username | OpsChain username | yes | — |
| opschain_password | OpsChain password | yes | — |
| opschain_project | Project code for the change | yes | "" |
| opschain_environment | Environment code for the change | yes | — |
| opschain_action | The action to perform during this change | yes | — |
| opschain_requestTimeout | opschain request timeout | no | 60000 |
| opschain_action_metadata | The metadata to store along with this change | yes | "" |
| opschain_git_remote | Git Remote name to use on the OpsChain Project | yes | origin |
| opschain_git_rev | The Git revision (branch/tag/commit) for the change | yes | ${GITHUB_SHA} |
| opschain_github_username | The GitHub Username with which to authenticate | yes | — |
| opschain_github_pat | The GitHub Privileged Access Token with which to authenticate | yes | — |
Outputs
no outputs