Difference between revisions of "Terraform data source: terraform remote state"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
== See also == | == See also == | ||
| + | * {{terraform state}} | ||
* {{Terraform data sources}} | * {{Terraform data sources}} | ||
* {{Terraform}} | * {{Terraform}} | ||
[[Category:Terraform]] | [[Category:Terraform]] | ||
Revision as of 10:41, 16 February 2022
terraform_remote_state
Controlled Remote State Access feature in Terraform Cloud and Terraform Enterprise, users now have a new way to establish granular controls for state accessibility.
Related
See also
- Terraform state:
terraform [ state | replace-provider | mv ],backend.tf, Remote state backends to manage Terraform state, State locking,terraform force-unlock - Terraform data sources:
aws_vpc,template_file,aws_subnet_ids,terraform remote state,aws_eks_cluster,aws_ami, aws_availability_zones, aws_partition, archive_file - Terraform, OpenTofu, Terrakube.org, Installation, Terraform AWS, Terraform GCP, Terraform commands, Terraform Cloud, Terraform Enterprise (TFE), HCL, HIL, meta-arguments, providers, modules, resource, provisioners, data sources, backends: remote backends, examples, configuration files, state files, variables, types, Terraform Registry, conditionals:
depends_on, functions, Blocks, dynamic blocks, errors, Terragrunt, Terraformer, Terratest, Terraform certifications, Terraform map type, Terraform Associate, Terraform: list type,TF_VAR_, TF_LOG, Terraform provider versioning, Terraform Style Conventions, Required version, Terraform plugin, Terraform Named Values, tags, Changelog,tfsec, tflint, Operators, Expressions:for, splat, Debugging, Namespaces, Terraform Landing Zones, CDKTF, Atmos
Advertising:
