actions-marketplace-validations/Armory Continuous Deployment-as-a-Service

CD-as-a-Service enables declarative continuous deployment, with a GitOps experience and advanced deployment strategies.

Trust Signals

workflow.ymlSHA-pinned

uses: actions-marketplace-validations/armory_cli-deploy-action@867ccd1c583707bee8df8fad8cc320bc42a6e9a9 # no releases — HEAD as of 2026-07-10

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
path-to-file	Path to the configuration YAML file used to configure your deployment	yes	—
applicationName	extra args to the deployment start command	no	—
addContext	extra context params to the deployment start command	no	—
withScmFile	Path to the YAML file containing the SCM values associated with the deployment	no	—
clientId	ClientId for Armory Cloud	yes	—
clientSecret	ClientSecret for Armory Cloud	yes	—
audience	Intended audience of requests that will use your Armory Cloud authentication token. Is deployHostUrl by default	no	https://api.cloud.armory.io
tokenIssuerUrl	Armory Cloud authentication provider url	no	https://auth.cloud.armory.io/oauth
deployHostUrl	Location of the Armory Cloud API which will handle your deployment	no	api.cloud.armory.io
waitForDeployment	Boolean flag (true\|false) determining if the action should wait for the deployment to complete. "false" by default.	no	false

name	description
DEPLOYMENT_ID	Unique deployment identifier - can be used to query the status of the deployment in cloud-console
LINK	Link to the cloud-console, where you can check the state of the workflow and advance it to the next stages
RUN_RESULT	If deployment was triggered with 'waitForDeployment=true' flag, this variable will contain final status of the deployment - one of [SUCCEEDED, CANCELLED, FAILED, UNKNOWN (error)]