Managing Configuration Source Providers

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).

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

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.

Bitbucket Cloud:

• https://bitbucket.org/

Bitbucket Server:

• my-private-bitbucket-server.example.com

GitHub:

• GitHub Enterprise Cloud: https://github.com/org-name
• GitHub Enterprise Server: https://hostname/api/v3
• GitHub Free for Organization: https://github.com/org-name
• GitHub Free for User Accounts: https://github.com
• GitHub team: https://github.com/team-name

GitLab:

• GitLab.com product: https://gitlab.com/
• GitLab installation (relative URL): https://example.com/gitlab
• GitLab installation (subdomain): https://gitlab.example.com/

Apply tags to resources to help organize them according to your business needs. You can apply tags when you create a resource, and you can update a resource later to add, revise, or remove tags. For general information about applying tags, see Resource Tags.