Creating an Apply Job

• Console
• CLI
• API

• 1. On the Stacks list page, select the stack that you want to work with. If you need help finding the list page or the stack, see Listing Stacks.
  2. On the stack's details page, select Apply.
  3. (Optional) In the Apply panel, edit the default name for the job. Avoid entering confidential information.
  4. (Optional) For Apply job plan resolution, select the name of the latest generated plan job. Only the latest generated plan job is available. If no plan job has been generated for this stack, then only the default value is available (Automatically approve). For more information about Automatically approve, see Auto-Approve Option for Terraform Apply Command.
  5. To retrieve the latest versions available from the configured source of Terraform providers, select Show advanced options and select Upgrade provider versions.
     The stack must be Terraform 0.14 or later, and if the stack is older, it must be upgraded to use Terraform Registry.This step is required if provider versions in the Terraform configuration changed since the last time a job was run on the stack. Dependency lock files are automatically managed for new and updated stacks. Providers are updated within the version constraints of the Terraform configuration.
  6. To generate detailed log content for debugging, select Show advanced options and select the log level that you want from Detailed log level.
     For more information, see Debugging Terraform.
  7. To adjust the maximum number of concurrent operations as Terraform walks the graph, select Show advanced options and edit the value for Maximum number of parallel operations. (Default: 10.) Use this option to speed up the job.
     Note
     
     A high value might cause throttling of resources. For example, consider a Terraform configuration that defines hundreds of compute instances. An Apply job attempts to create as many instances as possible at the same time. In this example, a value of 100 might cause throttling by the Compute service.
  8. To fetch the latest state before running the job, select Show advanced options and select Refresh resource states before checking for differences.

     Use this option to refresh the state first. For example, consider using this option with an Apply job that you intend to run on manually updated (existing) infrastructure.

     Note
     
     Refreshing the state can affect performance. If the configuration includes several resources, consider not using this option.
  9. (Optional) Select Show advanced options and assign tags to the job.
     • Tag namespace: To add a defined tag, select an existing namespace. To add a free-from tag, leave the value blank.
     • Tag key: To add a defined tag, select an existing tag key. To add a free-form tag, type the key name that you want.
     • Tag value: Type the tag value that you want.
     • Add tag: Click to add another tag.
  10. Select Apply.

  The apply job is created. The new job is listed under Jobs.

• Use the oci resource-manager job create-apply-job command and required parameters to run an apply job.

  oci resource-manager job create-apply-job [OPTIONS]

  For a complete list of parameters and values for CLI commands, see the Command Line Reference for Resource Manager.

  Examples

  Example 1: Reference a plan job.

  oci resource-manager job create-apply-job --execution-plan-strategy <plan_job_ocid> --stack-id <stack_ocid>

  Example 2: Automatically approve (don't reference a plan job).

  oci resource-manager job create-apply-job --execution-plan-strategy AUTO_APPROVED --stack-id <stack_ocid>

• Use the CreateJob operation to create an apply job.

  For an example of the operation part of the request, see CreateApplyJobOperationDetails.