You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to #2503 , #1209 , #2335 and #2390
Currently when output is printed via terraform output or just attached to terraform apply, it is not escaped at all, e.g.
Outputs:
test-count = 3
test-region = us-east-1
I know it would be best to just allow formatting the output as JSON, but at the same time it would be nice to just make the current output format compatible with HCL - i.e. escape output properly per specific type:
I guess even JSON format will need to take similar approach based on object type, so it probably doesn't make a huge difference whether this is solved via JSON or current HCL format.
The text was updated successfully, but these errors were encountered:
Outputs aren't really meant to be in any re-consumable format. I'm supportive of a JSON output format for things, but don't think the general human-readable output should be in any such format.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
May 1, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Related to #2503 , #1209 , #2335 and #2390
Currently when output is printed via
terraform output
or just attached toterraform apply
, it is not escaped at all, e.g.I know it would be best to just allow formatting the output as JSON, but at the same time it would be nice to just make the current output format compatible with HCL - i.e. escape output properly per specific type:
https://github.com/hashicorp/hcl/blob/master/hcl/object.go#L15-22
I guess even JSON format will need to take similar approach based on object type, so it probably doesn't make a huge difference whether this is solved via JSON or current HCL format.
The text was updated successfully, but these errors were encountered: