Skip to content

Commit

Permalink
Remove conflicts between source/destination IP ranges from google_com…
Browse files Browse the repository at this point in the history
…pute_firewall to support Local IP Range Support Preview.
  • Loading branch information
rosmo committed Dec 9, 2022
1 parent cf77957 commit 4504f49
Showing 1 changed file with 0 additions and 6 deletions.
6 changes: 0 additions & 6 deletions mmv1/products/compute/api.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3742,9 +3742,6 @@ objects:
traffic that has destination IP address in these ranges. These ranges
must be expressed in CIDR format. Only IPv4 is supported.
item_type: Api::Type::String
conflicts:
- source_ranges
- source_tags
- !ruby/object:Api::Type::Enum
name: 'direction'
description: |
Expand Down Expand Up @@ -3840,8 +3837,6 @@ objects:
connection does not need to match both properties for the firewall to
apply. Only IPv4 is supported. For INGRESS traffic, one of `source_ranges`,
`source_tags` or `source_service_accounts` is required.
conflicts:
- destination_ranges
item_type: Api::Type::String
- !ruby/object:Api::Type::Array
name: 'sourceServiceAccounts'
Expand Down Expand Up @@ -3879,7 +3874,6 @@ objects:
item_type: Api::Type::String
conflicts:
- source_service_accounts
- destination_ranges
- target_service_accounts
- !ruby/object:Api::Type::Array
name: 'targetServiceAccounts'
Expand Down

0 comments on commit 4504f49

Please sign in to comment.