-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Support for google_access_context_manager_service_perimeter ingress/egress policies #4535
Conversation
The new contents is the output from running `bundle exec compiler`, with the `output: false` attributes stripped.
This is a straight copy of the same config from ServicePerimeter.
Hello! I am a robot who works on Magic Modules PRs. I have detected that you are a community contributor, so your PR will be assigned to someone with a commit-bit on this repo for initial review. Thanks for your contribution! A human will be with you soon. @slevenick, please review this PR or find an appropriate assignee. |
I'm having trouble running the TF provider tests, but opening this PR in case any review comments come out of it in the meantime. |
- !ruby/object:Api::Product::Version | ||
name: beta | ||
base_url: https://accesscontextmanager.googleapis.com/v1/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although the new properties are available in the v1 API version, the documentation indicates they are not GA (see the docs), hence why the same base_url is used for both ga and beta versions.
This looks like a duplicate of #4509 |
Closing this as a duplicate of #4509. |
Adds beta support for egress and ingress policies to VPC Service Control perimeters.
Resolves Terraform provider Issue 8412.
If this PR is for Terraform, I acknowledge that I have:
make test
andmake lint
to ensure it passes unit and linter tests.Release Note Template for Downstream PRs (will be copied)