To use resources from a given provider, you need to include some informationĪbout it in your configuration. In production we recommend constraining the acceptable provider versions in the configuration's provider requirements block, to make sure that terraform init does not install newer versions of the provider that are incompatible with the configuration. Providers are released separately from Terraform itself, and have their own version numbers. See the provider publishing documentation. Menu in the header to change which version you're viewing.įor details about writing, generating, and previewing provider documentation, Provider documentation in the Registry is versioned you can use the version 'Documentation' link in a provider's header to browse its documentation. Includes documentation for a wide range of providers developed by HashiCorp, third-party vendors, and our Terraform community. Provider DocumentationĮach provider has its own documentation, describing its resource Providers for most major infrastructure platforms. Is the main directory of publicly available Terraform providers, and hosts Has its own release cadence and version numbers. Providers are distributed separately from Terraform itself, and each provider Generating random numbers for unique resource names. Providers can also offer local utilities for tasks like Most providers configure a specific infrastructure platform (either cloud or

What Providers DoĮach provider adds a set of resource typesĮvery resource type is implemented by a provider without providers, Terraform Additionally, some providers requireĬonfiguration (like endpoint URLs or cloud regions) before they can be used. Terraform configurations must declare which providers they require so that Terraform relies on plugins called providers to interact with cloud providers, Hands-on: Try the Perform CRUD Operations with Providers tutorial.

Dashlane india pricing