Kusto(data explorer) for Synapse

adamyager commented 2 years ago

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

We do need to leverage Data Explorer(Kusto) for Synapse. Today SQL and Spark are in TF but not data explorer.

New or Affected Resource(s)

It would mirror this very closely https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/synapse_spark_pool

Potential Terraform Configuration

resource "azurerm_synapse_kusto_pool" "example" { name = "example" synapse_workspace_id = azurerm_synapse_workspace.example.id node_size_family = "MemoryOptimized" node_size = "Small" cache_size = 100

auto_scale { max_node_count = 50 min_node_count = 3 }

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

Dependency on this https://github.com/Azure/azure-sdk-for-go/issues/17179#issue-1150757233

adamyager commented 2 years ago

@mybayern1974 I was told my the Azure SDK for go that we would need to use this version of the SDK but its not an upstream dependency as I originally thought. I dont think this version is used in the RM so it would need to be upgraded too.

https://github.com/Azure/azure-sdk-for-go/tree/main/services/preview/synapse/mgmt/v2.0/synapse All the Kusto items are here.

adamyager commented 1 year ago

@mybayern1974 any ideas on getting some eyes on this?

ramioh commented 1 year ago

It's been more than a year now since data explorer pools for Synpase were released. It would be really great if this became natively supported by Terraform's Azure RM provider. Right now, the only terraform-based way to do it is by invoking Azure Cli commands from a local-exec resource, and then we are not really using Terraform, its state management, or its dependency management capabilities. I am also surprised this issue didn't get that many upvotes. Is what I am doing really that niche? I started to worry 😆

hashicorp / terraform-provider-azurerm