-
Notifications
You must be signed in to change notification settings - Fork 446
[Fix] Use latest etag for access_control_rule_set
#4622
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
Conversation
access_control_rule_set
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.
Tested internally, changes outside of Terraform are now correctly shown. LGTM
Cc: @gauthamsunjay - can you look? |
a12e2d0
to
7c6d734
Compare
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
## Changes <!-- Summary of your changes that are easy to understand --> We use tagging.py which automatically infers version from NEXT_CHANGELOG. Updating it to patch as we already had SDK generation and we need to release: #4622 ## Tests <!-- How is this tested? Please see the checklist below and also describe any other relevant tests --> N/A - [ ] `make test` run locally - [ ] relevant change in `docs/` folder - [ ] covered with integration tests in `internal/acceptance` - [ ] using Go SDK - [ ] using TF Plugin Framework
Changes
Tests
Updated Unit tests
make test
run locallydocs/
folderinternal/acceptance