Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
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