feat: more dns providers, including 'other'

[Morriz]

Checklist

• Architecture Design Records have been added as adr/*.md and appended to list in adr/_index.md, if applicable.
• The values-schema.yaml file and test/** fixtures have been updated to reflect code changes, if applicable.
• The OpenApi Schema from redkubes/otomi-api project is compatible with definitions from values-schema.yaml file, if applicable.

[j-zimnowoda]

Looking good. Just few remarks. Looking forward to next iteration. Cheers.

[Morriz]

Fixed also many validation issues which were still quite a lot.
Can you re-review @j-zimnowoda ?

[j-zimnowoda]

Fixed also many validation issues which were still quite a lot.
Can you re-review @j-zimnowoda ?

I looked again, only two remarks, related with previous comments

[j-zimnowoda]

Could you perform migration tests for values with azure dns settings?

[Morriz]

Could you perform migration tests for values with azure dns settings?

What do you mean? Unit tests are in place for migration tests.

[Morriz]

external-dns is still an app that allows for raw values as ppl might want to add more filters

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	Secret	Commit	Filename
4062983	Generic High Entropy Secret	51a3b08	tests/fixtures/env/secrets.settings.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
4062983	Generic High Entropy Secret	51a3b08	tests/fixtures/env/secrets.settings.yaml	View secret
4062983	Generic High Entropy Secret	7fb6043	tests/fixtures/env/secrets.settings.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>