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

Add Ingress and Egress functionality to VPC Service Controls #8722

Closed
ngodec opened this issue Mar 18, 2021 · 5 comments
Closed

Add Ingress and Egress functionality to VPC Service Controls #8722

ngodec opened this issue Mar 18, 2021 · 5 comments

Comments

@ngodec
Copy link

ngodec commented Mar 18, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

There is a new feature in VPC Service Controls that allows configuring extra rules for the service perimeters: https://cloud.google.com/vpc-service-controls/docs/ingress-egress-rules. This solves a number of immediate needs for everyone who has a more complex setup, and would be great to have it in terraform!

New or Affected Resource(s)

  • google_access_context_manager_service_perimeter
  • google_access_context_manager_access_level

Or new resources:

  • google_access_context_manager_ingress_rule
  • google_access_context_manager_egress_rule

Potential Terraform Configuration

resource "google_access_context_manager_egress_rule" "allow-aggregated-logging" {
  parent        = "accessPolicies/${google_access_context_manager_access_policy.access-policy.name}"
  perimeter   = "accessPolicies/${google_access_context_manager_access_policy.access-policy.name}/perimeters/sensitive1"
  egressto = {
      serviceName = "logging.googleapis.com"
      methodsSelectors = [
        "LoggingServiceV2.WriteLogEntries",
        "LoggingService.WriteLogEntries",
      ]
      resources =  [ "projects/999" ]
  }
  egressFrom = {
    identityType = "ANY_IDENTITY"
  }
}

References

@ghost ghost added enhancement labels Mar 18, 2021
@apereira
Copy link

@ngodec
Copy link
Author

ngodec commented Mar 22, 2021

Found that this is a duplicate of #8412

@ngodec
Copy link
Author

ngodec commented Mar 22, 2021

Thanks for that @apereira ! I guess now to wait for #8723 to be released :)

@rileykarson
Copy link
Collaborator

Closing as dupe of #8412

@ghost
Copy link

ghost commented Apr 22, 2021

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Apr 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants