Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GCP IAM API can have delayed propagation #111

Open
gw0 opened this issue May 20, 2021 · 0 comments
Open

GCP IAM API can have delayed propagation #111

gw0 opened this issue May 20, 2021 · 0 comments

Comments

@gw0
Copy link

gw0 commented May 20, 2021

Problem:
It seems there is a delay between when new GCP SA keys are generated (created on-demand using this Vault GCP secrets engine) and when they are accepted by other GCP services (like GCS). If your app attempts to use them before they are propagated, it fails.

Expected behaviour:
Of course one would expect GCP SA keys to be valid from the moment they are issued. But on the other hand, the GCP secrets engine should return either an error or valid credentials. The simplest solution would be to have a delay option to wait for a short time before it returns the credentials (i.e. 5 seconds should probably be enough), such that they have time to propagate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant