Skip to content
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

Don't run GPC VPC discovery tasks when the subnet was already specified. #149

Merged

Conversation

chusopr
Copy link
Contributor

@chusopr chusopr commented Sep 18, 2023

The VPC network and subnet discovery tasks that run in roles/platform/tasks/initialize_gcp.yml may require additional privileges and are only required to find a subnet to deploy to when not specified. When the subnet is already specified in infra.gcp.vpc.subnet_id those tasks are not required.

This PR skips those tasks when the subnet is already specified. I needed it for a project where listing GCP subnets was not allowed, so it was already tested.
I also tested that it still works as before when you don't provide a subnet.

@wmudge wmudge added this to the Release 2.1.0 milestone Oct 5, 2023
@wmudge wmudge modified the milestones: Release 2.1.0, Release 2.2.0 Nov 2, 2023
@wmudge wmudge modified the milestones: Release 2.2.0, Release 2.3.0 Nov 20, 2023
@jimright jimright self-assigned this Dec 20, 2023
@wmudge wmudge requested a review from a team December 20, 2023 16:44
@jimright jimright added the enhancement New feature or request label Dec 20, 2023
Copy link
Contributor

@jimright jimright left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested with pre-existing VPC and subnet. Confirmed that these tasks are skipped and deployment is successful. Approved.

@wmudge wmudge merged commit 27d7bf2 into cloudera-labs:devel Dec 22, 2023
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request validated
Development

Successfully merging this pull request may close these issues.

3 participants