outgoing-webhooks validation

[OrNovo]

IAC-224 CXO: Validation Webhooks for CRDs

[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	GitGuardian status	Secret	Commit	Filename
14149094	Triggered	Generic High Entropy Secret	1e3e9e9	config/manager/manager.yaml	View secret
14149094	Triggered	Generic High Entropy Secret	16dcc54	config/manager/manager.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.

---

^{🦉 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.}

[github-actions]

Previous Coverage	26.8% of statements
New Coverage	26.8% of statements
Patch Coverage	0.0% of changed statements (0/0)

---

^{Coverage provided by https://github.com/seriousben/go-patch-cover-action}

[assafad1]

@OrNovo Please consider adding testcases to e2e/outbound_webhook_test.go, or in a new file, to validate the new functionality (even in a follow-up).

[OrNovo]

@OrNovo Please consider adding testcases to e2e/outbound_webhook_test.go, or in a new file, to validate the new functionality (even in a follow-up).

I resolved the issued you mentioned. The e2e-tests will be added on a different PR.

[assafad1]

@OrNovo Thanks for addressing my comments, really nice work here!

[github-actions]

🎉 This PR is included in version 0.2.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀