fix: follow up on database certificates properties renaming

[yann-soubeyrand]

Hi,

It seems that the renaming of the database certificates properties broke the creation of the secret when certificates are provided to the charts. This PR is my attempt to fix it.

Definition of Ready

• I am happy with the code
• Short description of the feature/issue is added in the pr description
• PR is linked to the corresponding user story
• Acceptance criteria are met
• All open todos and follow ups are defined in a new ticket and justified
• Deviations from the acceptance criteria and design are agreed with the PO and documented.
• No debug or dead code
• My code has no repetitions
• Documentation/examples are up-to-date
• All non-functional requirements are met
• If possible, the test configuration is adjusted so acceptance tests cover my changes

[eliobischof]

Thanks for this fix @yann-soubeyrand, LGTM 🚀

If you'd like us to send you a small gift in return, please shoot us a message to [email protected]

[eliobischof]

@yann-soubeyrand please merge the base branch back into the PRs branch or allow us to commit changes to your branch

[yann-soubeyrand]

@eliobischof done! I cannot see the “Allow edits from maintainers checkbox”, is it something that has to be activated in the repository settings first?

[eliobischof]

@eliobischof done! I cannot see the “Allow edits from maintainers checkbox”, is it something that has to be activated in the repository settings first?

🤷‍♂️ idk, but I could merge now.
Thank you.

[yann-soubeyrand]

Thanks @eliobischof! As for the gift, if you can fix these issues I would be more than grateful 😊

zitadel/zitadel#9141
zitadel/zitadel#9200

[eliobischof]

Thanks @eliobischof! As for the gift, if you can fix these issues I would be more than grateful 😊

zitadel/zitadel#9141
zitadel/zitadel#9200

I raised #9141 internally