fix: Indent ENABLE_WEBHOOKS env variable under container

[rouke-broersma]

Summary by CodeRabbit

• Configuration Updates
  • Refined environment variable configuration for the EMQX operator controller manager.
  • Added conditional WATCH_NAMESPACE environment variable support.
  • Reorganized environment variable placement for improved clarity.

[coderabbitai]

Walkthrough

The pull request modifies the deployment configuration for the EMQX operator's controller manager. The changes involve repositioning the ENABLE_WEBHOOKS environment variable within the containers section and conditionally adding a WATCH_NAMESPACE environment variable. The overall structure of the deployment configuration is maintained, with the environment variables organized for enhanced clarity.

Changes

File	Change Summary
deploy/charts/emqx-operator/templates/controller-manager.yaml	- Moved ENABLE_WEBHOOKS environment variable within containers section - Added conditional WATCH_NAMESPACE environment variable based on singleNamespace value

Possibly related PRs

• chore: can disable webhook in helm #1101: The changes in this PR involve the addition of a new configuration option for enabling or disabling webhooks, which is directly related to the repositioning of the ENABLE_WEBHOOKS environment variable in the main PR.

Poem

🐰 In YAML's dance, a rabbit's delight,
Environment vars shift left and right
Webhooks enabled, namespaces clear
Configuration tweaks bring coding cheer!
A hop of improvement, precise and neat 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 43679ce and c5b6005.

📒 Files selected for processing (1)

• deploy/charts/emqx-operator/templates/controller-manager.yaml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• deploy/charts/emqx-operator/templates/controller-manager.yaml

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.