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

added time_sleep and dependancies on shared vpc attachment #608

Merged
merged 3 commits into from
Jul 29, 2021
Merged

added time_sleep and dependancies on shared vpc attachment #608

merged 3 commits into from
Jul 29, 2021

Conversation

rm-paoloventriglia
Copy link
Contributor

This fixes #607

Service project needs to be added to the VPC-SC perimeter before it get attached to the SharedVPC (that is part of the same VPC-SC Perimeter) else you get a Error 403: Request is prohibited by organization's policy. vpcServiceControlsUniqueIdentifier

Adding google_access_context_manager_service_perimeter_resource.service_perimeter_attachment[0] to depends_on for "google_compute_shared_vpc_service_project" "shared_vpc_attachment" doesn't work either as the VPC-SC api seems to be eventually consistent.

Adding a 5s time_sleep although not ideal fixes the issue.

@rm-paoloventriglia rm-paoloventriglia requested a review from a team as a code owner July 26, 2021 22:36
@comment-bot-dev
Copy link

comment-bot-dev commented Jul 26, 2021

Thanks for the PR! 🚀
✅ Lint checks have passed.

Copy link
Member

@bharathkkb bharathkkb left a comment

Choose a reason for hiding this comment

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

Thanks for the PR @paolo-rm

modules/core_project_factory/main.tf Show resolved Hide resolved
@google-cla
Copy link

google-cla bot commented Jul 29, 2021

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

@rm-paoloventriglia
Copy link
Contributor Author

@googlebot I signed it!

@morgante
Copy link
Contributor

@paolo-rm Please make sure you sign the CLA with these emails:

@rm-paoloventriglia
Copy link
Contributor Author

@morgante I have signed it with [email protected] and added that address to github and verified it plus added it to git commits for this repo. Is that ok? My company has two emails and only have a Google account with [email protected]. Sorry haven't contribute before, I was a bit confused. Is this ok now?

@morgante
Copy link
Contributor

@paolo-rm Yep, it's working now!

@morgante morgante merged commit 59b7b96 into terraform-google-modules:master Jul 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Creating project in the same perimeter as the the shared vpc causes error
4 participants