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
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish: Builds with regional secrets fail to validate and can't be used, so Builds should be able to use regional secrets.
How this might work: While submitting the build, it is failing to pull the regional secrets, so Builds should be able to use regional secrets.
Presuming this is because the cloud build validation isn't aware of regional secrets and does not gather them when getting the list of secrets for a build, thus the secret is declared not valid.
If applicable, reasons why alternative solutions are not sufficient: N/A
Other information (workarounds you have tried, documentation consulted, etc):
Reproducing this behavior, which happens using both global build pools as well as a private pool in the same region as the regional secret.