[bitnami/external-dns] Cannot use both `txtEncrypt.aesKey` and `cloudflare.secretName`
Name and Version
bitnami/external-dns 8.0.2
What architecture are you using?
None
What steps will reproduce the bug?
Try to install the helm chart with the values I provided.
Are you using any custom parameters or values?
provider: cloudflare
cloudflare:
secretName: cloudflare-token
txtEncrypt:
enabled: true
aesKey: some-random-key
What do you see instead?
Installation fails with the following error:
cloudflare.apiKey is required if cloudflare.apiToken is not provided
Additional information
The external-dns.createSecret template in _helpers.tpl forces the secret defined in secret.yaml to be created if the txtEncrypt.aesKey is provided. The cloudflare block in the latter seems to assume that it will only be reached if cloudflare.secretName isn't set and thus either cloudflare.apiKey or cloudflare.apiToken need to be set.
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
hi, can we reopen this? It's still an issue.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Please reopen, this is still valid. PR for a fix here: #32360
Thank you for submitting the associated Pull Request. Your contribution is greatly appreciated!