glueops/OpenTofu - Continuous Delivery

Abstracts multiple OpenTofu actions from @dflook and provides a streamlined workflow with some basic customization

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Activelast commit Jun 30, 2026
License
None

Pinned Snippet

workflow.ymlSHA-pinned
uses: glueops/github-actions-opentofu-continuous-delivery@b1808ba89f6c3b0f038ac2ceb97583ac70590489 # v6.1.1

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

namedescriptionrequireddefault
pathPath to the tofu configurationno.
workspaceName of the tofu workspacenodefault
backend_configList of backend config values to set, one per lineno""
backend_config_filePath to a backend config fileno""
variablesVariable definitionsno""
var_fileList of var file paths, one per lineno""
parallelismLimit the number of concurrent operationsno0
labelA friendly name for this planno""
targetList of resources to target for the apply, one per lineno""
replaceList of resources to replace if an update is required, one per lineno""
destroyCreate and apply a plan to destroy all resourcesnofalse
backend_typeThe backend plugin nameyes
add_github_commentPost a sticky comment on the PR with the plan (inlined when it fits, otherwise a link to the tofu-plan.txt artifact)notrue
ENABLE_DANGEROUS_AUTO_APPLY_MODEIf enabled, any changes including: Destroy, Apply, Replace will be automatically approved.nofalse
namedescription
tofuThe tofu version used by the configuration
changesIf the generated plan would update any resources or outputs this is set to `true`, otherwise it's set to `false`.
to_addThe number of resources that would be added by this plan
to_changeThe number of resources that would be changed by this plan
to_destroyThe number of resources that would be destroyed by this plan
plan_pathPath to a file in the workspace containing the generated plan in an opaque binary format.
text_plan_pathPath to a file in the workspace containing the generated plan in human readable format. This won't be set if the backend type is `remote` and `auto_approve` is `true`
json_plan_pathPath to a file in the workspace containing the generated plan in JSON format. This won't be set if the backend type is `remote`.
run_idIf the root module uses the `remote` or `cloud` backend in remote execution mode, this output will be set to the remote run id.
failure-reasonThe reason for the build failure. May be `apply-failed` or `plan-changed`.