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

TractusX Helm Chart: setting either the vault.azure.clientsecret _or_ vault.azure.certificate does not work #168

Closed
paullatzelsperger opened this issue Mar 29, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@paullatzelsperger
Copy link
Contributor

Describe the bug

Setting the vault.azure.clientsecret value to authenticate against an Azure KevVault does not work, because it always gets overwritten by vault.azure.certificate.

The reason is that the respective environment variables (EDC_VAULT_CERTIFICATE and EDC_VAULT_CLIENTSECRET) are always set, even when vault.azure.certificate is not configured, and they have a default value of "" (empty string).

Then, the AzureVaultExtension checks if the certificate path is null, which it isn't (because it's ""), and tries to interpret the empty string as certificate path, which obviously fails.

Possible Implementation

setting the environment variables only if the respective Values exist:

# only set the env var if config value not null
{{- if .Values.vault.azure.secret }}
- name: "EDC_VAULT_CLIENTSECRET"
  value: {{ .Values.vault.azure.secret | quote }}
{{- end }}
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: Done
Development

No branches or pull requests

1 participant