wcfoki.blogg.se - Runjs vs make

#Runjs vs make update#
#Runjs vs make upgrade#
#Runjs vs make full#

You can use the following sources as runs list query parameters.

#Runjs vs make upgrade#

This is most commonly used to upgrade terraform state versions. Specifies the run performed an apply with no changes to resources. Specifies the run destroyed all objects, regardless of configuration changes.

#Runjs vs make update#

Specifies the run was instructed to execute a plan to update Terraform state. Indicates the run completed with both plan and apply phases. Indicates the run completed without an apply phase. You can reference the following list of possible operation modes and use them as runs list query parameters. The run operation specifies the Terraform execution mode. This is a final state.Ī workspace admin forcefully canceled the run. Terraform has applied the changes specified in the plan. Terraform is applying the changes specified in the plan. However, in Terraform Enterprise this status will be more common due to the self-hosted nature. In Terraform Cloud, you should seldom see this status, as our aim is to always have capacity. This status indicates that the run should start as soon as the backend services that run terraform have available capacity. Once the changes in the plan have been confirmed, the run will transition to apply_queued.

This status only exists for plan-only runs and runs that produce a plan with no changes to apply. The post-plan phase of the run has completed. The post-plan phase of the run is in progress. The sentinel policy checking phase of a run has completed. The sentinel policy checking phase of a run is in progress.Ī sentinel policy has soft failed, and a user can override it to continue the run.Ī sentinel policy has soft failed for a plan-only run. The cost estimation phase of a run has completed. The cost estimation phase of a run is in progress. The planning phase of a run has completed. The planning phase of a run is in progress. Terraform Cloud is waiting for its backend services to start the plan. Terraform Cloud is queuing the run to start the planning phase. The pre-plan phase of the run has completed. The pre-plan phase of the run is in progress. Terraform Cloud has fetched the configuration from VCS and the run will continue. The run is waiting for Terraform Cloud to fetch the configuration from VCS. The initial status of a run after creation. The run state is found in, and you can reference the following list of possible states. This is useful for promoting known good code from one workspace to another.

Create and queue an apply on the run if the run can't be auto-applied.Īlternatively, you can create a run with a pre-existing configuration version, even one from another workspace.

Create a run on the workspace this is done automatically when a configuration file is uploaded.

Upload configuration files to the configuration version.

Create a configuration version on the workspace.

Performing a run on a new configuration is a multi-step process.

#Runjs vs make full#

Note: Before working with the runs or configuration versions APIs, read the API-driven run workflow page, which includes both a full overview of this workflow and a walkthrough of a simple implementation of it.