Oracle Cloud Infrastructure Documentation

Managing Configuration Source Providers

Remotely store Terraform configurations using configuration source providers in Resource Manager.

Note

For remote Terraform configurations in DevOps, see Creating a Stack from DevOps.

You can perform the following management tasks with configuration source providers:

Required IAM Policy

Use policies to grant access to configuration source providers in Resource Manager.

To manage configuration source providers, 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. To create a configuration source provider, you need manage orm-config-source-providers. To create a stack with an existing configuration source provider, you need manage orm-stacks and read orm-config-source-providers. If you're new to policies, see Getting Started with Policies and Common Policies.

Administrators: For common policies that give groups access to configuration source providers in Resource Manager, see Manage Configuration Source Providers (Securing Resource Manager).

Supported Products

Review the products supported for configuration source providers in Resource Manager.

Note

For product-specific prerequisites, see the product-specific instructions for creating configuration source providers. For example, for GitHub, see Creating a GitHub Configuration Source Provider.

Submodules are supported. When accessing a Terraform configuration in a repository with submodules, as when running an apply job on a stack that uses a configuration source provider in Git, Resource Manager recursively clones the repository.

A configuration source provider can be one of the following types:

  • Bitbucket
  • GitHub
  • GitLab

Following are the supported products for each type of configuration source provider.