out_azure_kusto: Azure Kusto Cloud Environment Support

[tanmaya-panda1]

This pull request updates the Azure Kusto output documentation to add support for configuring private and sovereign cloud environments. The main changes are new configuration options that allow users to specify custom endpoints and resource URLs for these environments.

Azure Kusto Cloud Environment Support:

• Added the cloud_name option to specify the Azure cloud environment (default: AzureCloud). For private clouds, users should set custom endpoints instead.
• Introduced cloud_login_host, cloud_kusto_scope, and cloud_kusto_resource options for specifying custom OAuth endpoints and resource URLs required for private or sovereign Azure clouds. These must be provided together when targeting such environments.

Summary by CodeRabbit

• Documentation
  • Added four new configuration options for Azure private and sovereign cloud environments, enabling customized authentication and resource management across different cloud deployments.

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation for Azure Kusto connector expanded with four new configuration keys supporting private and sovereign cloud deployments: cloud_name, cloud_login_host, cloud_kusto_scope, and cloud_kusto_resource. Each key includes descriptive text and default values to guide users.

Changes

Cohort / File(s)	Summary
Azure Kusto Documentation pipeline/outputs/azure_kusto.md	Added four new configuration parameters for Azure private/sovereign cloud support with descriptions and default values.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 Four new keys hop into view,
Cloud configurations fresh and new,
Azure realms both private and vast,
Documentation at last, at last!
Sovereign clouds now have their say,
Kusto connections light the way! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'out_azure_kusto: Azure Kusto Cloud Environment Support' accurately reflects the main change: adding Azure cloud environment configuration support to the Azure Kusto output connector documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

pipeline/outputs/azure_kusto.md (1)

63-66: Clarify when cloud_name vs custom endpoints apply.

Current wording could be read as requiring custom endpoints for all sovereign clouds. Consider clarifying that cloud_name covers public sovereign clouds (e.g., AzureUSGovernmentCloud), while custom endpoints are for private clouds or non-standard sovereign endpoints, and that custom endpoints override/replace cloud_name when set.

💡 Suggested wording tweak

-| `cloud_name`                           | Set the Azure cloud environment. Supported values: `AzureCloud` (default), `AzureChinaCloud`, `AzureUSGovernmentCloud`. For private clouds, set `cloud_login_host`, `cloud_kusto_scope`, and `cloud_kusto_resource` instead. | `AzureCloud`                   |
-| `cloud_login_host`                     | Custom OAuth login host for private/sovereign clouds (for example, `login.microsoftonline.eaglex.ic.gov`). When set, `cloud_kusto_scope` and `cloud_kusto_resource` must also be provided. | _none_                         |
-| `cloud_kusto_scope`                    | Custom Kusto OAuth scope for private/sovereign clouds (for example, `https://help.kusto.core.eaglex.ic.gov/.default`). When set, `cloud_login_host` and `cloud_kusto_resource` must also be provided. | _none_                         |
-| `cloud_kusto_resource`                 | Custom Kusto IMDS resource URL for private/sovereign clouds (for example, `https://api.kusto.core.eaglex.ic.gov/`). When set, `cloud_login_host` and `cloud_kusto_scope` must also be provided. | _none_                         |
+| `cloud_name`                           | Set the Azure cloud environment. Supported values: `AzureCloud` (default), `AzureChinaCloud`, `AzureUSGovernmentCloud`. Use custom endpoints only for private clouds or non-standard sovereign endpoints. | `AzureCloud`                   |
+| `cloud_login_host`                     | Custom OAuth login host for private clouds or non-standard sovereign endpoints (for example, `login.microsoftonline.eaglex.ic.gov`). When set, `cloud_kusto_scope` and `cloud_kusto_resource` must also be provided and take precedence over `cloud_name`. | _none_                         |
+| `cloud_kusto_scope`                    | Custom Kusto OAuth scope for private clouds or non-standard sovereign endpoints (for example, `https://help.kusto.core.eaglex.ic.gov/.default`). When set, `cloud_login_host` and `cloud_kusto_resource` must also be provided. | _none_                         |
+| `cloud_kusto_resource`                 | Custom Kusto IMDS resource URL for private clouds or non-standard sovereign endpoints (for example, `https://api.kusto.core.eaglex.ic.gov/`). When set, `cloud_login_host` and `cloud_kusto_scope` must also be provided. | _none_                         |

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@pipeline/outputs/azure_kusto.md` around lines 63 - 66, The docs are ambiguous
about when to use cloud_name vs custom endpoints; update the description for
cloud_name and the three custom fields (cloud_login_host, cloud_kusto_scope,
cloud_kusto_resource) to state that cloud_name covers built-in public/sovereign
Azure clouds (e.g., AzureCloud, AzureChinaCloud, AzureUSGovernmentCloud) and
that custom endpoints are only required for private or non-standard sovereign
environments, and that providing any of
cloud_login_host/cloud_kusto_scope/cloud_kusto_resource overrides/replaces
cloud_name for authentication and Kusto calls; ensure the text explicitly notes
the required co-dependency between cloud_login_host, cloud_kusto_scope, and
cloud_kusto_resource.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@pipeline/outputs/azure_kusto.md`:
- Around line 63-66: The docs are ambiguous about when to use cloud_name vs
custom endpoints; update the description for cloud_name and the three custom
fields (cloud_login_host, cloud_kusto_scope, cloud_kusto_resource) to state that
cloud_name covers built-in public/sovereign Azure clouds (e.g., AzureCloud,
AzureChinaCloud, AzureUSGovernmentCloud) and that custom endpoints are only
required for private or non-standard sovereign environments, and that providing
any of cloud_login_host/cloud_kusto_scope/cloud_kusto_resource
overrides/replaces cloud_name for authentication and Kusto calls; ensure the
text explicitly notes the required co-dependency between cloud_login_host,
cloud_kusto_scope, and cloud_kusto_resource.

---

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4a18664 and 04dc838.

📒 Files selected for processing (1)

• pipeline/outputs/azure_kusto.md

[eschabell]

Once the code PR merges, this is good to go.