Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S3 remote state use application/json Content-Type #3385

Merged
merged 1 commit into from
Oct 9, 2015
Merged

S3 remote state use application/json Content-Type #3385

merged 1 commit into from
Oct 9, 2015

Conversation

apparentlymart
Copy link
Contributor

The state is always JSON, in spite of the fact that this interface presents it as an opaque byte array. It's more helpful to those interacting with the state object outside of Terraform for it to have a more specific content-type.

This addresses #3342.

The state is always JSON, in spite of the fact that this interface
presents it as an opaque byte array. It's more helpful to those interacting
with the state object outside of Terraform for it to have a more specific
content-type.
@stack72
Copy link
Contributor

stack72 commented Oct 8, 2015

@apparentlymart This looks a really straight forward change that should get merged without any risk
:)

apparentlymart added a commit that referenced this pull request Oct 9, 2015
S3 remote state use application/json Content-Type
@apparentlymart apparentlymart merged commit fbfab83 into hashicorp:master Oct 9, 2015
@ghost
Copy link

ghost commented Apr 30, 2020

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 ghost locked and limited conversation to collaborators Apr 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants