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

Issue disabling gcp secrets #37

Closed
jclarksnps opened this issue May 24, 2019 · 3 comments · Fixed by #39
Closed

Issue disabling gcp secrets #37

jclarksnps opened this issue May 24, 2019 · 3 comments · Fixed by #39

Comments

@jclarksnps
Copy link

jclarksnps commented May 24, 2019

I'm having issues disabling the gcp secrets engine, its trying to delete a key it issued that no longer exists. Is there some way to force the delete from vault secrets disable gcp?

Full error when trying to disable:

There was an error disabling the gcp secrets engine at gcp/: failed to revoke "some-key" (1 / 2): failed to revoke entry: resp: &logical.Response{Secret:, Auth:, Data:map[string]interface {}{"error":"unable to delete service account key: googleapi: Error 403: Permission iam.serviceAccountKeys.delete is required to perform this operation on service account key projects/some-project/serviceAccounts/service-account-email/keys/key_id., forbidden"}, Redirect:"", Warnings:[]string(nil), WrapInfo:(*wrapping.ResponseWrapInfo)(nil)} err: .

@jclarksnps
Copy link
Author

I managed to get around this by forcing the revocation of any keys associated with the gcp backend by doing: vault lease revoke -force -prefix gcp/

@emilymye
Copy link
Contributor

Ah,, apparently in some specific cases key.get returns a 403 instead of 404. Fun! I'll put out a fix.

@jclarksnps
Copy link
Author

Thanks @emilymye

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

Successfully merging a pull request may close this issue.

2 participants