DXCDT-519: Improve DX for managing is_token_endpoint_ip_header_trusted
on auth0_client
resource
#796
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
馃敡 Changes
At the moment we only allow managing the
is_token_endpoint_ip_header_trusted
property of the client when the resource gets updated; on create it gets skipped. This unfortunately requires 2 terraform applies in combination with anauth0_client_credentials
resource.To avoid having to run 2 terraform applies, on create if the
is_token_endpoint_ip_header_trusted
is set, we default the authentication method (token_endpoint_auth_method
) of the client toclient_secret_post
.馃摎 References
馃敩 Testing
馃摑 Checklist