-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Store remote S3 state with JSON content type #3342
Comments
That is a very good point. 👍 I agree. |
Yeah, I'm not sure what I was thinking when I set it to application/json. #3385 fixes this. |
@radeksimko / @apparentlymart this can be closed now since #3385 fixes it |
…nerate-dr-secondary-token to be a POST rather than GET. This was reported by a customer and I confirmed that this should be a logical.UpdateOperation rather than ReadOperation (https://github.com/hashicorp/vault-enterprise/blob/24f2b961fdb300e7cfcaaa94e708509513bb54f3/vault/replication_api.go#L121). (hashicorp#3342)
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. |
Currently the state gets stored as
application/octet-stream
. Not sure if there was a reason for that, but if not, perhaps store it asapplication/json
so that when browsing in the AWS console, double-clicking won't require you to download the file (if your browser can readapplication/json
responses).If setting this as the default isn't appropriate, maybe another option could be to set it through something like
--backend-config="content-type=application/json"
.The text was updated successfully, but these errors were encountered: