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

Feature request-add-diagnostic-setting-data-explorer-kusto-cluster #1965

Closed
1 task done
raoafzalraza opened this issue Apr 19, 2024 · 0 comments · Fixed by #2031
Closed
1 task done

Feature request-add-diagnostic-setting-data-explorer-kusto-cluster #1965

raoafzalraza opened this issue Apr 19, 2024 · 0 comments · Fixed by #2031

Comments

@raoafzalraza
Copy link

raoafzalraza commented Apr 19, 2024

Is there an existing issue for this?

  • I have searched the existing issues

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

There no support for diagnostic setting for ADX (data_explorer), adding the fix for diagnostic setting for data_explorer (Kusto_Cluster)

resource "azurerm_kusto_cluster" "kusto" {

New or Affected Resource(s

azurerm_kusto_cluster

Potential Configuration file

module "diagnostics" {
source = "../../diagnostics"
for_each = try(var.settings.diagnostic_profiles, {})

resource_id = azurerm_kusto_cluster.kusto.id
resource_location = var.location
diagnostics = var.remote_objects.diagnostics
profiles = var.settings.diagnostic_profiles
}

References

No response

@arnaudlh arnaudlh linked a pull request Jul 23, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant