-
Notifications
You must be signed in to change notification settings - Fork 632
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
Properly send Access policy purpose justification settings #2836
Properly send Access policy purpose justification settings #2836
Conversation
changelog detected ✅ |
I can't figure out how to get a test case to fail for the thing I fixed. The problem was that the state was matching the config (and so the tests pass), but the actual policy in Cloudflare was wrong. The existing tests should catch it if the value itself is missing, but maybe @jacobbednarz you have a recommendation about how I can update the tests for this specific use case? |
generally you'd need to rely on a custom API call (example: https://github.com/cloudflare/terraform-provider-cloudflare/blob/master/internal/sdkv2provider/resource_cloudflare_access_group_test.go#L555) and perform your own checks. i do wonder if this sort of check belongs in the provider though or if there is something on the service side we could do instead. up to you to make the call either way. |
just sorting out entitlement issue for the acceptance tests and we should be good here
|
The account is correctly entitled, but it's missing a prereq step. To make use of that flag we need to have a setting enabled in the account. In the zt dash, settings > browser isolation > clientless web isolation > enable TBH I'm not sure if this is something we should do out of band or as a part of a test? If I need to add it to the test let me know and I'll figure out how to do that. |
thanks @jroyal 🙇 i've manually toggled it for now but if there is an API for it, i'd love to make it a part of the acceptance test flow so that we aren't reliant on any manual steps for the test suite to run but not a blocker here. acceptance tests all looking good now 👏
|
This functionality has been released in v4.17.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! |
fixes #2813
Probably need to update tests, but wanted to push this up real quick. I've tested this a lot locally and I'm not sure why we had the nil guards to start with. Removing them allows terraform to understand when the value is either missing or updated. If there is something i'm missing about why they should exist let me know.