For private clusters, do not use --create-subnetwork if it's multi-project profile #115
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since for shared-vpc - the network topology we use for multi-project profile, the subnetworks will be created before cluster creation, so for private cluster + shared vpc, if we also specify
--create-subnetwork
, we will get an error which saysCannot specify both --subnetwork and --create-subnetwork at the same time.
This PR updates to the logic to only add
--create-subnetwork
if it's single-project profile.