Difference between revisions of "Terraform state pull"
Jump to navigation
Jump to search
↑ https://stackoverflow.com/questions/59473690/how-to-extract-sensitive-output-variables-in-terraform
| Line 3: | Line 3: | ||
| − | terraform state pull | jq '.resources[] | select(.type == "[[aws_iam_access_key]]") | .instances[0].attributes' <ref>https://stackoverflow.com/questions/59473690/how-to-extract-sensitive-output-variables-in-terraform</ref> | + | [[terraform state]] pull | jq '.resources[] | select(.type == "[[aws_iam_access_key]]") | .instances[0].attributes' <ref>https://stackoverflow.com/questions/59473690/how-to-extract-sensitive-output-variables-in-terraform</ref> |
Revision as of 10:04, 27 February 2023
terraform state pull | jq '.resources[] | select(.type == "aws_iam_access_key") | .instances[0].attributes' [1]
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[untaint | fmt|apply|show|state|init | plan | console | output|validate|destroy|debug|import|providers|get|graph|workspaces|resource|login|-var-file|state mv|state pull|state push|state replace-provider|state rm|force-unlock|env|tfe|--version|remote-exec|delete on termination| deprecated commands |terraform --help]
Advertising:
