Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for EngineV3 in kusto_cluster #9695

Closed
kosinsky opened this issue Dec 4, 2020 · 3 comments
Closed

Support for EngineV3 in kusto_cluster #9695

kosinsky opened this issue Dec 4, 2020 · 3 comments

Comments

@kosinsky
Copy link
Contributor

kosinsky commented Dec 4, 2020

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

Kusto aka ADX announced public preview of EngineV3: "Kusto EngineV3 is Azure Data Explorer’s next generation storage and query engine. It's designed to provide unparalleled performance for ingesting and querying telemetry, logs, and time series data."

EngineType is a new property of ClusterProperties in 2020-09-18 of the Kusto API that allows to choose engine type during cluster creation.

New or Affected Resource(s)

  • azurerm_kusto_cluster

Potential Terraform Configuration

resource "azurerm_kusto_cluster" "test" {
  name                = "acctestkc%s"
  location            = azurerm_resource_group.test.location
  resource_group_name = azurerm_resource_group.test.name

  sku {
    name     = "Dev(No SLA)_Standard_D11_v2"
    capacity = 1
  }
  engine			  = "V3"
}

References

@jrauschenbusch
Copy link
Contributor

@kosinsky @mbfrahry I think this feature is now implemented and this ticket can be closed.

@kosinsky
Copy link
Contributor Author

kosinsky commented Mar 15, 2021

Yeas. It's done as #9696

@ghost
Copy link

ghost commented Apr 14, 2021

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Apr 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants