acemq-company/AceMQ infrastructure
Plan or apply a broker cutover with acemq-infra, without installing anything.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| command | validate, plan or apply. | yes | — |
| file | The deployment file to read. | yes | — |
| version | Which release to run, without the leading v. Defaults to the ref this action was used at, so @v0.4.0 runs 0.4.0 and the action and the binary cannot disagree. Give it a version explicitly when the action is used from a branch. | no | "" |
| dry-run | apply only: re-probe both clusters and rehearse every step, writing nothing. | no | false |
| assume-yes | apply only: consent to the run starting, which is what --yes does. It does not answer any question the run asks afterwards. | no | false |
| require-variables | validate only: an unset ${VAR} is an error rather than a warning. | no | false |
| args | Anything else to pass through, split on whitespace. | no | "" |
| working-directory | Where to run, for relative paths in the deployment file. | no | . |
| verify-attestation | Check the binary against the build provenance GitHub recorded when the release was built, with `gh attestation verify`. Off by default only because it needs a token: pass github-token and turn it on, and see docs/install.md for what it buys over the checksum. | no | false |
| github-token | A token, for verify-attestation and for release downloads on a rate-limited runner. | no | "" |
| summary | Put what the tool printed into the job summary, where a plan can be read. | no | true |
Outputs
| name | description |
|---|---|
| exit-code | 0 ok, 1 findings or a refused or stopped run, 2 a bad command line. |
| output-file | A file holding everything the tool printed, for a later step to read. |