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

provider: allow configuring x-auth-service-key individually #1907

Merged
merged 1 commit into from Sep 13, 2022

Conversation

jacobbednarz
Copy link
Member

Following in the footsteps of
#1768 (comment), this introduces the ability to set the x-auth-service-key individually without setting another authentication mechanism. Prior to 3.18, you could set multiple and the internals looked busted but sometimes worked...and other times didn't.

This is hopefully the last case we need to tidy up to correctly set the auth correctly for the request that users are making.

Closes #1905

Following in the footsteps of
#1768 (comment),
this introduces the ability to set the x-auth-service-key individually without
setting another authentication mechanism. Prior to 3.18, you could set multiple
and the internals looked busted but sometimes worked...and other times didn't.

This is hopefully the last case we need to tidy up to correctly set the auth
correctly for the request that users are making.

Closes #1905
@github-actions
Copy link
Contributor

changelog detected ✅

@jacobbednarz jacobbednarz merged commit 7f7df2b into master Sep 13, 2022
@jacobbednarz jacobbednarz deleted the allow-user-service-key-for-auth branch September 13, 2022 03:59
@github-actions github-actions bot added this to the v3.24.0 milestone Sep 13, 2022
github-actions bot pushed a commit that referenced this pull request Sep 13, 2022
@github-actions
Copy link
Contributor

This functionality has been released in v3.24.0 of the Terraform Cloudflare Provider.

Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@mattmichal
Copy link

@jacobbednarz there may still be an authentication info case that is not covered. I opened #1939 based on what I'm seeing in 3.24.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Querying OriginCACertificate fails with "could not read response body"
2 participants