[kusto] Add command example

[cxznmhdcxz]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @cxznmhdcxz,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[Copilot]

Pull Request Overview

This PR enhances the help content for the kusto attached-database-configuration create command by adding a usage example.

• Introduces an examples section under the command help.
• Provides a full CLI invocation demonstrating all available flags.
• Ensures users have a concrete reference for creating an attached database configuration.

Comments suppressed due to low confidence (2)

src/kusto/azext_kusto/manual/_help.py:712

• Align the examples key under the same indent level used by type and short-summary (e.g., six spaces) so the YAML block parses correctly.

    examples:

src/kusto/azext_kusto/manual/_help.py:716

• [nitpick] Indent this continuation line (and any subsequent lines) under the first argument in the code block (for example, with two extra spaces) to make the multi-line example easier to read.

--database-name "KustoDatabase" --default-principals-modification-kind "Union" --table-level-sharing-properties external-tables-to-exclude="ExternalTable2" external-tables-to-include="ExternalTable1" materialized-views-to-exclude="MaterializedViewTable2" materialized-views-to-include="MaterializedViewTable1" tables-to-exclude="Table2" tables-to-include="Table1"

[github-actions]

Hi @cxznmhdcxz

Release Suggestions

Module: kusto

• Please log updates into to src/kusto/HISTORY.rst
• Update VERSION to 1.0.0 in src/kusto/setup.py

Notes

• For more info about extension versioning, please refer to Extension version schema