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

Align KeycloakClient Resource Secret Reference in Argo CD #68

Open
Artem-Zahumonnyi opened this issue Apr 10, 2024 · 0 comments
Open

Align KeycloakClient Resource Secret Reference in Argo CD #68

Artem-Zahumonnyi opened this issue Apr 10, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@Artem-Zahumonnyi
Copy link
Contributor

Describe the bug
The KeycloakClient resources experience a discrepancy in Argo CD between the declared secret and the secret after Custom Resource (CR) modifications. Specifically, a declared secret like "secret: keycloak-client-nexus-secret" is automatically changed to "secret: '$keycloak-client-nexus-secret:clientSecret'" upon deployment, causing a diff in Argo CD.

To Reproduce

What did you do?

Deployed a KeycloakClient resource through Argo CD with the secret field defined as:

secret: keycloak-client-nexus-secret

What did you expect to see?

I expected the KeycloakClient resource to maintain the declared secret reference without automatic modifications.

What did you see instead? Under which circumstances?

After deployment through Argo CD, the CR modifies the secret reference to:

secret: '$keycloak-client-nexus-secret:clientSecret'

This change causes a persistent diff in Argo CD, indicating a discrepancy between the declared and live states.

@Artem-Zahumonnyi Artem-Zahumonnyi added the bug Something isn't working label Apr 10, 2024
@Artem-Zahumonnyi Artem-Zahumonnyi self-assigned this Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Todo
Development

No branches or pull requests

1 participant