-
Notifications
You must be signed in to change notification settings - Fork 4.7k
gce: use set type where order does not matter #17377
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
base: master
Are you sure you want to change the base?
gce: use set type where order does not matter #17377
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
deff2da
to
93e782b
Compare
Starting small with FirewallRule Allowed and SourceRanges, but this should be easier than explicitly handling values where order does not matter.
93e782b
to
ee0b15b
Compare
(This isn't urgent, I think this is a nice-to-have to address this problem going forwards, we can discuss in office hours) Note one (negative?) consequence of this is that the rules are string-sorted in terraform. I think that's a good thing going forwards, but it will cause a text-level diff in the terraform output (though not a cloud-level diff, because terraform also knows order doesn't matter here) |
/retest |
@justinsb: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Starting small with FirewallRule Allowed and SourceRanges fields,
but this should be easier than explicitly handling values
where order does not matter.