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

sops/keyservice: properly fallback to default #597

Merged
merged 3 commits into from
Mar 25, 2022
Merged

Conversation

hiddeco
Copy link
Member

@hiddeco hiddeco commented Mar 25, 2022

(AMD64) image for testing available at: hiddeco/kustomize-controller:fix-azkv-fallback-dc5486f

Potentially addresses: #595

@hiddeco hiddeco added bug Something isn't working area/sops SOPS related issues and pull requests labels Mar 25, 2022
Copy link
Member

@pjbgf pjbgf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

This solves a regression bug introduced in `v0.22.0`, which caused the
keyservice to not properly fall back to the default for Azure Key Vault
decryption requests.

A couple of nitpicks that I ran into while inspecting the code have
been adressed as well.

Signed-off-by: Hidde Beydals <hello@hidde.co>
Signed-off-by: Hidde Beydals <hello@hidde.co>
Signed-off-by: Hidde Beydals <hello@hidde.co>
@hiddeco
Copy link
Member Author

hiddeco commented Mar 25, 2022

Although there is no positive confirmation yet that this solves the issue described in #595, I am going ahead and merge this, as I am confident it addresses at least one variant of the issue.

@hiddeco hiddeco merged commit cf9b0fc into main Mar 25, 2022
@hiddeco hiddeco deleted the fix-azkv-fallback branch March 25, 2022 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/sops SOPS related issues and pull requests bug Something isn't working
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants