[ONBOARD] Kusto Add DataExplorer Operations

[amih90]

Overview

Introduces Azure Data Explorer (Kusto) operations, including:

• Cluster management: List and Get for Kusto clusters.
• Database management: List databases, List and Schema tables within a cluster.
• Query execution: Run KQL Query, Sample against databases and retrieve results.

Usage

# List Kusto clusters in a subscription
azmcp kusto cluster list --subscription <subscription>

# Get details for a Kusto cluster
azmcp kusto cluster get --subscription <subscription> --cluster-name <cluster-name>

# List databases in a Kusto cluster
azmcp kusto database list [--cluster-uri <cluster-uri> | --subscription <subscription> --cluster-name <cluster-name>]

# List tables in a Kusto database
azmcp kusto table list [--cluster-uri <cluster-uri> | --subscription <subscription> --cluster-name <cluster-name>]
                                --database-name <database-name> \

# Retrieves the schema of a specified Kusto table.
azmcp kusto table schema [--cluster-uri <cluster-uri> | --subscription <subscription> --cluster-name <cluster-name>]
                                  --database-name <database-name> \
                                  --table <table-name>

# Query a Kusto database
azmcp kusto query [--cluster-uri <cluster-uri> | --subscription <subscription> --cluster-name <cluster-name>]
                           --database-name <database-name> \
                           --query "<kql-query>"

# Retrieves a sample of data from a specified Kusto table.
azmcp kusto sample [--cluster-uri <cluster-uri> | --subscription <subscription> --cluster-name <cluster-name>]
                            --database-name <database-name> \
                            --table <table-name> \
                           [--limit <limit>]

Testing

• 80% unit test coverage for all Kusto commands and base command logic.
• Manual validation against live Kusto clusters.

Notes

• No breaking changes to existing services or commands.

[joshfree]

Tagging as Do Not Merge until this is no longer WIP

[amih90]

@joshfree PR is ready for review.

[danield137]

@amih90 you beat me to it :)
I think it would be better to stick to the cluster name and not the uri, for simplicity sake.
Here's how you'd get it:

private async Task<ICslQueryProvider> CreateKustoQueryClient(string clusterName, string? tenant = null)
{
    var credential = await GetCredential(tenant);
    var subscription = await _subscriptionService.GetSubscription(clusterName, tenant);
    var cluster = await GetCluster(subscription, clusterName);
    if (cluster == null)
    {
        throw new Exception($"Cluster '{clusterName}' not found in subscription '{subscription.Id}'");
    }

    var uri = cluster.Data.ClusterUri.ToString() ??
        throw new Exception($"Could not retrieve URI for cluster '{clusterName}'");

    var connectionStringBuilder = new KustoConnectionStringBuilder(uri)
        .WithAadAzureTokenCredentialsAuthentication(credential);

    return KustoClientFactory.CreateCslQueryProvider(connectionStringBuilder);
}

[danield137]

also, tagging my open issue here: #45

[danield137]

Had another discussion about this.
To clarify, the problem I have boils down to how do we make sure the agent "knows" how to map a cluster name to a cluster uri?

Right now, the description for get cluster does not clearly state that it has the uri, or that you need to use it, and I'm somewhat concerned that an agent might mistakenly come up with their own uri schema...

So, the options I see are:

1. Change the argument to name. This has the drawback that a user can't easily point to a specific service if they want to just drop a uri, as names are not easily mapped to a uri (and vice versa).
2. Add another command GetClutserUri. This should be straightforward for the agent to figure out the connection.
3. Add a more explicit description for the GetCluster command, stating it returns a cluster_uri among other things.

I'm leaning towards (2), but (3) could be enough. I'll leave the decision to @xiangyan99 who is assigned :)

[joshfree]

On track to merge Tuesday, May 6th

[danield137]

@joshfree , @amih90 is going to have one last round of fixes tomorrow (Israel Time), so hopefully, tomorrow EOD (PST) should be good to go.

[joshfree]

Live tests need to also be added to the PR /cc @hallipr

[joshfree]

Thank you for the contribution! Kusto support is awesome!