Feature request: google_access_context_manager_service_perimeter_ingress_policy and google_access_context_manager_service_perimeter_egress_policy resources

[wmuizelaar]

Affected Resource(s)

• google_access_context_manager_service_perimeter_ingress_policy
• google_access_context_manager_service_perimeter_egress_policy

Hi,

I filed GoogleCloudPlatform/k8s-config-connector#727 to add more granular support for dealing with VPC SC resources. This includes separate resources for ingress policies and egress policies, following the same pattern as the current google_access_context_manager_service_perimeter_resource resource in the Terraform provider.

Could these seperate resources be implemented?

For google_access_context_manager_serivce_perimeter_ingress_policy, the schema would be the same as the existing ingress_policies block in the perimeter-resource, and for the google_access_context_manager_service_perimeter_egress_policy the schema would be the same as the egress_policies block.

References

• b/258778964

[AlfatahB]

google_access_context_manager_service_perimeter has ingress_policies and egress_policies fields. I was able to find gcloud commands for setting/updating ingress and egress policies for a service perimeter during creation/updation of that particular service parameter. But, I was unable to find gCloud command or an API doc for configuring ingress and egress policies separately.

[rileykarson]

Note: While initial revisions were submitted in GoogleCloudPlatform/magic-modules#7762 and GoogleCloudPlatform/magic-modules#7765 and released, they didn't work as intended (as reported by #14425) and are planned to be reworked substantially.

[roaks3]

@melinath per your comment on b/258778964, should we forward a new issue to the service team?

[melinath]

@roaks3 I think we are still holding this issue - attn @c2thorn @hao-nan-li to confirm.

[hao-nan-li]

This feature should've been completed. GoogleCloudPlatform/magic-modules#8038

[melinath]

cool, closing as completed in that case.

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.