-
Notifications
You must be signed in to change notification settings - Fork 612
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
fix: change mTLS associated hostnames to a set #3498
Conversation
changelog detected ✅ |
24ba41d
to
393e8ef
Compare
Looks good to me! |
internal/sdkv2provider/schema_cloudflare_access_mutual_tls_certificate.go
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the changes you're making here are basically what TypeSet
is built for. i'd suggest we swap to that instead and remove the additional schema functions here.
Signed-off-by: Matt Provost <mprovost@cloudflare.com>
I thought what I was doing felt wrong! Thanks for pointing me in the right direction. Updated and ready for re-review :) |
Hi @jacobbednarz, can we get this reviewed for the next release? |
the acceptance tests are failing here (and on
|
From the error message, is it possible that |
I think I agree with @bporter816 that it looks like the |
Ah yes, I think I misread the docs on that function. Another thing I wasn't sure about is if things like this indexing still work: Line 131 in 4708b62
|
nice find. after fixing that (and adding a check in the tests for future runners), this is all now passing
|
This functionality has been released in v4.41.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! |
The API doesn't order mTLS associated hostnames in any meaningful way. This can cause drift as seen in #3436. We can mitigate this by ignoring associated hostname changes, when the only thing that has changed is the ordering.
I tried a number of other approaches including sorting the list that is returned from the API and sorting the incoming associated hostname list, but none of that type of stuff worked.
fixes #3436