Oracle Cloud Infrastructure Documentation

Managing Stacks and Jobs

This topic describes how to create, edit, and delete stacks as well as work with jobs, including generating and applying execution plans.

Warning

Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Oracle Cloud Infrastructure Console, API, or CLI.

Prerequisites

  • IAM policies: To manage stacks and jobs, you must be given the required type of access in a policy  written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which compartment  you should work in.

    Administrators: For common policies that give groups access to stacks and jobs, see Policies for Managing Stacks and Jobs. For a complete list of Resource Manager permissions, see Details for Resource Manager. Policies for managing accessed resource types are also required.

    Important

    Policies for managing Oracle Cloud Infrastructure resources are also required for Resource Manager operations that access resources. For example, running an apply job on a stack that includes Compute instances and subnets requires policies that grant you permissions for those resource types, in the compartments where you want to provision the resources. To see examples of policies for managing Oracle Cloud Infrastructure resources, see Common Policies.

  • Terraform configuration file: To create or update a stack, you must have a valid Terraform configuration file. See Terraform Configurations for Resource Manager and Writing Terraform Configurations.

Tagging Resources

You can apply tags to your resources to help you organize them according to your business needs. You can apply tags at the time you create a resource, or you can update the resource later with the desired tags. For general information about applying tags, see Resource Tags.

Moving Resources to a Different Compartment

You can move stacks from one compartment to another. When you move a stack to a new compartment, its associated jobs move with it. After you move the stack to the new compartment, inherent policies apply immediately and affect access to the stack and associated jobs through the Console. For more information, see Managing Compartments.

Using the Console

To create a stack
To view stacks
To edit a stack
To manage tags for a stack
To move a stack to a different compartment
To delete a stack
To view jobs and job details
To manage tags for a job
To generate an execution plan (run a plan job)
To view the job log
To update the configuration for a stack
To download job information
To run an apply job
To view the state of a job
To import an existing Terraform state file (run an import job)
To release a stack's resources (run a destroy job)

Using the CLI

This section provides basic sample CLI commands for managing stacks and jobs. For information about using the CLI, see Command Line Interface (CLI). For a complete list of flags and options available for CLI commands, see CLI Help.

To create a stack
To list stacks in a compartment
To list full details of a stack
To delete a stack
To generate an execution plan (run a plan job)
To review an execution plan (view the log for a plan job)
To update an execution plan (update the configuration for a stack)
To run an apply job
To download or view job information
To import an existing Terraform state file (run an import job)
To inspect resources in a compartment
To release a stack’s resources (run a destroy job)

Using the API

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

Use these API operations to manage stacks:

Use these API operations to manage jobs:

Use these API operations to manage work requests:

This topic has moved. Please update your bookmarks.

This topic has moved. Please update your bookmarks.