About 114,000 results
Open links in new tab
  1. Terraform Registry

    RegistryPlease enable Javascript to use this application

  2. Docs overview | hashicorp/aws | Terraform | Terraform Registry

    This configuration prevents Terraform from returning any tag key matching the prefixes in any tags attributes and displaying any configuration difference for those tag values.

  3. azurerm_resource_group | Resources - Terraform Registry

    This Feature Toggle is disabled in 2.x but enabled by default from 3.0 onwards, and is intended to avoid the unintentional destruction of resources managed outside of Terraform (for example, …

  4. Docs overview | hashicorp/kubernetes - Terraform Registry

    Terraform providers for various cloud providers feature resources to spin up managed Kubernetes clusters on services such as EKS, AKS and GKE. Such resources (or data-sources) will have …

  5. hashicorp/aws | Terraform Registry

    Top downloaded aws modules Modules are self-contained packages of Terraform configurations that are managed as a group.

  6. Docs overview | hashicorp/azuread - Terraform Registry

    We recommend using either a Service Principal or Managed Identity when running Terraform non-interactively (such as when running Terraform in a CI/CD pipeline), and authenticating using …

  7. aws_lambda_function | Resources - Terraform Registry

    You can fix the problem two ways: 1) updating the function's role to another role and then updating it back again to the recreated role, or 2) by using Terraform to taint the function and …

  8. azurerm_storage_account | Resources - Terraform Registry

    Terraform uses Shared Key Authorisation to provision Storage Containers, Blobs and other items - when Shared Key Access is disabled, you will need to enable the storage_use_azuread flag …

  9. azurerm_monitor_diagnostic_setting - Terraform Registry

    This is a Terraform specific Resource ID which uses the format {resourceId}|{diagnosticSettingName}

  10. Resources | hashicorp/azuread - Terraform Registry

    Unlike the Azure Portal, applications created with the Terraform AzureAD provider do not get assigned a default user_impersonation scope. You will need to include a block for the …