Tenant operator: fix nextcloud secret issue

[giorio94]

Description

This PR fixes the creation of the secret containing the nextcloud credentials, avoiding to apply the base64 enconding. Additionally, it introduces a new test ensuring the correctness of the secret creation.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

• Ginkgo test
• Staging environment

[kingmakerbot]

Hi @giorio94. Thanks for your PR.

I am @kingmakerbot.
You can interact with me issuing a slash command in the first line of a comment.
Currently, I understand the following commands:

• /rebase: Rebase this PR onto the master branch
• /merge: Merge this PR into the master branch
• /hold: Adds hold label to prevent merging with /merge
• /unhold: Removes the hold label to allow merging with /merge
• /deploy-staging: Deploy a staging environment to test this PR
• /undeploy-staging: Manually undeploy the staging environment

Make sure this PR appears in the CrownLabs changelog, adding one of the following labels:

• kind/breaking: 💥 Breaking Change
• kind/feature: 🚀 New Feature
• kind/bug: 🐛 Bug Fix
• kind/cleanup: 🧹 Code Refactoring
• kind/docs: 📝 Documentation

[giorio94]

/deploy-staging

[kingmakerbot]

Your staging environment has been correctly deployed/updated!

• Frontend: check it out at https://410.staging.crownlabs.polito.it
• Operators: add the 'crownlabs.polito.it/operator-selector=staging-410' label to your tenant

[palexster]

Do we have a way to test it? I think it could be useful to protect it.

[giorio94]

/hold

I will try to add an appropriate test

[GabriFila]

lgtm

[giorio94]

/unhold

[giorio94]

/merge

[kingmakerbot]

Your staging environment has been correctly teared-down!