Difference between revisions of "Terraform state mv"
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
== See also == | == See also == | ||
* {{terraform state}} | * {{terraform state}} | ||
| − | * {{ | + | * {{Terraform}} |
[[Category:Terraform]] | [[Category:Terraform]] | ||
Revision as of 09:05, 8 February 2022
Examples
- Move a resource into a module:
terraform state mv packet_device.worker module.worker.packet_device.worker
Related terms
- Block type called moved
See also
- Terraform state:
terraform [ state | replace-provider | mv ],backend.tf, Remote state backends to manage Terraform state, State locking,terraform force-unlock - 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:
