Status Update
No update yet.
Comments
ba...@google.com
kk...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback. Thank you for your understanding and collaboration.
Thanks & Regards,
Ashalatha
Google Cloud Support
Description
Managing multiple VPC Service Controls (VPC SC) perimeters can be challenging, especially for daily operations. This complexity is compounded when multiple administrators, across different time zones, are involved, and when admins leave organizations.
Current Limitation:
Google Cloud Platform (GCP) currently only supports integer-based indexes for perimeter rules. This presents several issues:
Identification Challenges: Integer-based indexes do not provide sufficient information about the purpose of each rule, making it difficult to understand and manage them.
Automation Difficulties: Automating the management of perimeters via API calls is cumbersome. Tracking the purpose of each rule is hard, especially if a rule is deleted or altered, leading to confusion about which services are governed by which rules.
Proposed Feature:
To address these challenges, we propose the following enhancements:
String-Based Indexes: Implement support for string-based indexes for perimeter rules, allowing administrators to include descriptive identifiers. This would make it easier to understand the purpose and scope of each rule.
Metadata for Rules: Allow adding metadata or tags to each rule. This would enable administrators to add notes or descriptions about the rule’s purpose and the services it manages.
Improved API Support: Enhance API capabilities to support string-based indexes and metadata. This would facilitate easier automation and management of perimeter rules, ensuring that each rule’s purpose can be tracked and understood, even when modifications occur.