Added Ingress and Egress Rules for Standard and Dry Run

[aweberlopes]

Hello Guys,

i added my code and checked the Contributing Guidelines.

I tested the VPC SC in a Demo Organization and mostly functions work similar like on the ressource.

Please be kindly its my first pull request on GitHub so maybe i missing something.

[google-cla[bot]]

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).

:memo: 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

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[comment-bot-dev]

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

[aweberlopes]

@googlebot I signed it!

[aweberlopes]

@morgante Can you provide me the info where the Cloud Build Job fails that i can fix the issue I can not test it localy in my env because i can not delete access policy it would delete all existing perimeter.

[aweberlopes]

Hello together is here happening something?

[morgante]

Hi this is is the test failure:

       module.example.module.access_context_manager_policy.google_access_context_manager_access_policy.access_policy: Destroying... [id=580200975946]
       module.example.module.access_context_manager_policy.google_access_context_manager_access_policy.access_policy: Destruction complete after 1s

       Error: cannot destroy instance without setting deletion_protection=false and running `terraform apply`

[aweberlopes]

So tests are successful. Can somebody have a look on it?

[aweberlopes]

@morgante Is something missing here?

[aweberlopes]

will fix the rest tomorrow @morgante thanks for the sugesstions and fixes

[aweberlopes]

@morgante so simplified it can you check again?

[aweberlopes]

Okay will have a look thanks.

[bchazalet]

this looks useful. I'll definitely try it out once released.

[bchazalet]

i've been testing this branch with success on a project of mine