-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
make vm_count in google_compute_resource_policy as optional #6694
make vm_count in google_compute_resource_policy as optional #6694
Conversation
TestAccComputeResourcePolicy_attached is failing (without clear error) but it's also is failing on main branch. |
Hello! I am a robot who works on Magic Modules PRs. I've detected that you're a community contributor. @c2thorn, a repository maintainer, has been assigned to assist you and help review your changes. ❓ First time contributing? Click here for more detailsYour assigned reviewer will help review your code by:
You can help make sure that review is quick by running local tests and ensuring they're passing in between each push you make to your PR's branch. Also, try to leave a comment with each push you make, as pushes generally don't generate emails. If your reviewer doesn't get back to you within a week after your most recent change, please feel free to leave a comment on the issue asking them to take a look! In the absence of a dedicated review dashboard most maintainers manage their pending reviews through email, and those will sometimes get lost in their inbox. |
Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are. Diff report:Terraform GA: Diff ( 1 file changed, 2 insertions(+), 2 deletions(-)) |
Tests analyticsTotal tests: Action takenTriggering VCR tests in RECORDING mode for the tests that failed during VCR. Click here to see the failed testsTestAccComputeForwardingRule_update|TestAccDataSourceGoogleServiceAccountIdToken_basic |
mmv1/products/compute/api.yaml
Outdated
@@ -13012,18 +13012,16 @@ objects: | |||
properties: | |||
- !ruby/object:Api::Type::Integer | |||
name: 'vmCount' | |||
at_least_one_of: | |||
- group_placement_policy.0.vm_count | |||
conflicts: |
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.
From what I understand the at_least_one_of
restriction actually allowed both vm_count
and availability_domain_count
to be set in the same config. Changing this to conflicts
now introduces a new restriction that would make configs that did that invalid, thus a breaking change.
Could these fields absolutely not both be set? I would lean towards removing the restrictions entirely and letting the API handle the validation.
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.
These 2 fields can't be set (there is API validation for this). But you are right, it will be breaking change from TF perspective and right now it's better to remove all restrictions and rely on API validation.
Commit was updated.
caa1c87
to
3bebeea
Compare
Tests analyticsTotal tests: All tests passed in REPLAYING mode |
fixes hashicorp/terraform-provider-google#11483
If this PR is for Terraform, I acknowledge that I have:
make test
andmake lint
to ensure it passes unit and linter tests.Release Note Template for Downstream PRs (will be copied)