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.

Sign up for GitHub

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

Jump to bottom

sops/keyservice: properly fallback to default #597

Merged
merged 3 commits into from
Mar 25, 2022
Merged

sops/keyservice: properly fallback to default #597

merged 3 commits into from
Mar 25, 2022
+20 −17

Commits on Mar 25, 2022

  1. sops/keyservice: properly fallback to default 

    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 <[email protected]>
    @hiddeco
    hiddeco committed Mar 25, 2022
    Configuration menu
    Copy the full SHA
    069a106 View commit details
    Browse the repository at this point in the history

  2. build: configure --load for build via default 

    Signed-off-by: Hidde Beydals <[email protected]>
    @hiddeco
    hiddeco committed Mar 25, 2022
    Configuration menu
    Copy the full SHA
    e97ec3b View commit details
    Browse the repository at this point in the history

  3. Bump version of source-controller CRDs 

    Signed-off-by: Hidde Beydals <[email protected]>
    @hiddeco
    hiddeco committed Mar 25, 2022
    Configuration menu
    Copy the full SHA
    dc5486f View commit details
    Browse the repository at this point in the history