inprod/InProd Run Changesets

Execute InProd changesets to manage Genesys Cloud configuration as code

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stale
License: None

Inputs

name	description	required	default
api_key	InProd API key for authentication. Can also be set via INPROD_API_KEY environment variable.	no	—
base_url	Base URL of the InProd service (e.g., https://your-company.inprod.io). Can also be set via INPROD_BASE_URL environment variable.	no	—
changeset_file	Path to changeset YAML/JSON file, or a glob pattern matching multiple files (e.g., changesets/*.yaml). Files are sorted alphabetically by filename and processed sequentially.	yes	—
environment	Target environment name or ID (overrides environment field in changeset YAML)	no	—
validate_before_execute	Validate the changeset before executing (default: true)	no	true
validate_only	Only validate the changeset without executing (default: false)	no	false
polling_timeout_minutes	Maximum minutes to wait for task completion (default 10 minutes = 600 seconds)	no	10
execution_strategy	How to process multiple matched files. 'per_file': each file goes through validate -> execute -> poll before the next file starts. 'validate_first': validate all files first, then execute each sequentially. Only relevant when changeset_file matches multiple files.	no	per_file
fail_fast	Whether to stop processing remaining files when one fails. 'true': stop immediately on first failure. 'false': continue processing all files and report all failures at the end.	no	false
changeset_variables	Changeset variables in KEY=VALUE format (one per line). Allows injecting secrets from GitHub Secrets without storing in version control. See README for examples.	no	—

Outputs

name	description
status	Aggregate status across all files. Reports the worst status: FAILURE > TIMEOUT > REVOKED > SUCCESS > SUBMITTED.
result	JSON array of per-file results, each containing file, status, result, and error fields.