-
Notifications
You must be signed in to change notification settings - Fork 2
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
Cannot update existing secrets from the 1.3.0 version #32
Labels
bug
Something isn't working
Comments
Regression in v1.3.0, while no secret is selected by the selectors, it fails to create an empty target Secret. |
@antoineozenne-at-leocare The regression should be fixed in v1.3.1, could you give it another try? |
Now it works, thank you @RichardChen820! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I updated from version
1.2.0
to1.3.0
, but I have the following error for all my secrets (with a verbosity to 5):I noticed that the
existingSecrets
variable is no longer a pointer in the version1.3.0
inAppConfiguration-KubernetesProvider/internal/controller/appconfigurationprovider_controller.go
Line 239 in 26d0122
I think this could be the cause of my problem. I did not change anything in my
AzureAppConfigurationProvider
resources which usesecret.auth.workloadIdentity.managedIdentityClientIdReference
.The text was updated successfully, but these errors were encountered: