-
Notifications
You must be signed in to change notification settings - Fork 118
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
support following 302 redirects #60
Comments
I'm using http provider v2.1.0 with terraform v0.15.3 and it does follow a redirect. I tested it with an output.
GitHub releases respond with HTTP 302 to some other location. The output contains the correct YAML, but it also prints a warning Edit: found an actually more fitting issue here: #72 - sorry |
I have a similiar problem with a google sheet integration: for example this test sheet: gsheet
then after a
If you do a
If you skip the -L Location option curl will also "fail" and give the same message as the http-provider. So the http provider is not doing this redirect. Here a more detailed view of the curl with A
So could it be that http-provider only supports 302 redirects (as in the example from @toabi ) but not 307 ones? |
I have this issue as well. |
I found a workaround for 307 that should basically work for any redirect that gives you the redirect url in the output response. |
I'm using data "http" "someyaml" {} to fetch official crds/yamls for deploying to kubernetes. Some of these yamls send a 302 redirect that the http client is not following. It would be nice to expose a follow redirects argument to provide this control.
The text was updated successfully, but these errors were encountered: