DLP API blocked by “constraints/gcp.resourceLocations” [155032238]

Fixed

Feature Request

Status Update

No update yet.

Description

sa...@google.com

created issue #1

Apr 27, 2020 05:37AM

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:
Org. policy (constraints/gcp.resourceLocations) can restrict access to "global" API like DLP, causing a HTTP/403 PERMISSION_DENIED error.

How this might work:
Having the possibility to select a location different than "global" for DLP API.

If applicable, reasons why alternative solutions are not sufficient:
In DLP API there is a "locationId" parameter which is shown as “Reserved for future extensions” but after further investigation it does not look fully implemented for DLP as yet, or not being a valid workaround at the moment.

Other information (workarounds you have tried, documentation consulted, etc):
N/A

Comments

sa...@google.com <sa...@google.com> Apr 27, 2020 05:38AM

Assigned to gc...@google.com.

pe...@nos.pt <pe...@nos.pt> #2Jul 12, 2022 04:41PM

This has been fixed now using version 25.3.0: setSelectedItemId() is now available

mi...@google.com <mi...@google.com> #3Aug 24, 2022 11:33PM

Marked as fixed.

setSelectedItemId API is added from support library version 25.3.0.
Hence closing this issue.

Issue 155032238

Description

Issue summary

Comments

sa...@google.com <sa...@google.com> Apr 27, 2020 05:38AM

pe...@nos.pt <pe...@nos.pt> #2Jul 12, 2022 04:41PM

mi...@google.com <mi...@google.com> #3Aug 24, 2022 11:33PM

Add comment

Issue metadata