Assigned
Status Update
No update yet.
Comments
ba...@google.com
ba...@google.com
Hello,
Thanks for reaching out to us!
The Product Engineering Team has been made aware of your feature request, and will address it in due course. Though we can't provide an ETA on feature requests nor guarantee their implementation, rest assured that your feedback is always taken very seriously, as it allows us to improve our products. Thank you for your trust and continued support to improve Google Cloud Platform products.
In case you want to report a new issue, please do not hesitate to create a new
ba...@google.com
ba...@google.com
to...@ocado.com
I've found out that this feature was the only publicly accessible way of telling which dependencies API has (this has been confirmed by GCP Support). There is no info in the public docs, logs do not present any logical sense (APIs just randomly pops out in the logs), only Google's internal docs and teams were able to locate which API enabled a legacy API in our projects. Please consider solution to this problem by restoring this feature or providing constantly updated documentation.
th...@richemont.com
Indeed there doesn't seems to be any way to check for dependencies between services, and that make is harder to understand how services are working together
Description
I find it extremely peculiar that the
Serviceresource as returned bygcloud services list --enabled --format=jsonno longer shows service dependencies. Historically, this API exposed both the dependencies and the associated IAM grants to Google-controlled service accounts. These two data made it possible for us to use the authoritativegoogle_project_iam_policywithout needing much manual intervention which, for an organization with ±100 projects, is extremely valuable.We're getting by with an old mapping which, although of course falling further and further behind reality, still eliminates a lot of toil.