![]() ![]() self-serve-billing - Allows an organization to pay via credit card using the in-app billing UI.run-tasks - Allows an organization to use run tasks.private-module-registry - Allows an organization to publish and use modules with the private module registry.Affects the runs, plans, and applies endpoints. operations - Allows an organization to perform runs within Terraform Cloud.cost-estimation - Allows an organization to access cost estimation.configuration-designer - Allows an organization to use the Configuration Designer.audit-logging - Allows an organization to access audit trails.Affects the agent pools, agents, and agent tokens endpoints. agents - Allows isolated, private or on-premises infrastructure to communicate with an organization in Terraform Cloud.The following entitlements are available: The show entitlement set endpoint can return information about an organization's current entitlements, which is useful if your client needs to change its interface when a given feature isn't available. If an organization doesn't have the necessary entitlement to use a given feature, Terraform Cloud returns a 404 error for API requests to any endpoints devoted to that feature. ![]() These entitlements determine which Terraform Cloud features the organization can use. Terraform Cloud is available at multiple pricing tiers (including free), which offer different feature sets.Įach organization has a set of entitlements that corresponds to its pricing tier. They should not be logged, nor shared with untrusted parties. ![]() It is important to treat these URLs themselves as secrets. This is a broadly accepted pattern for secure access. Instead, each URL includes a securely generated secret and is only valid for 25 hours.įor example, the state versions api returns a field named hosted-state-download, which is a URL of this form: Unlike the Terraform Cloud API, this service does not require that a bearer token be submitted with each request. Terraform Cloud relies on a HashiCorp-developed blob storage service for storing statefiles and multiple other pieces of customer data, all of which are documented on our data security page. The organization token cannot perform plans and applies. This is intended for automating the management of teams, team membership, and workspaces. Organization tokens - each organization can have one API token at a time.This is intended for performing plans and applies via a CI/CD pipeline. Team tokens - each team can have one API token at a time.User tokens - each Terraform Cloud user can have any number of API tokens, which can make requests on their behalf.There are three kinds of tokens available: The 401 status code is reserved for problems with the authentication token forbidden requests with a valid token result in a 404. If the token is absent or invalid, Terraform Cloud responds with HTTP status 401 and a JSON API error object. Use the HTTP header Authorization with the value Bearer. AuthenticationĪll requests must be authenticated with a bearer token. ![]() The changelog tracks changes to the API for Terraform Cloud and Terraform Enterprise. HashiCorp provides a stability policy for the Terraform Cloud API, ensuring backwards compatibility for stable endpoints. It can't create or approve runs in response to arbitrary events, but it's a useful tool for managing your organizations, teams, and workspaces as code. Note: Before planning an API integration, consider whether the tfe Terraform provider meets your needs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |