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 [thing] #23673

Closed
1 task done
williamarobinson opened this issue Oct 24, 2023 · 3 comments · Fixed by #24258
Closed
1 task done

Support for [thing] #23673

williamarobinson opened this issue Oct 24, 2023 · 3 comments · Fixed by #24258

Comments

@williamarobinson
Copy link

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 and review the contribution guide to help.

Description

azurerm_cost_anomaly_alert needs the ability to be identified by subscription. Without this, a multi-account strategy would require access and provider at each subscription

New or Affected Resource(s)/Data Source(s)

azurerm_cost_anomaly_alert

Potential Terraform Configuration

subscription

References

No response

@williamarobinson
Copy link
Author

resource "azurerm_cost_anomaly_alert" "example" {
name = "alertname"
subscription = "subscription ID"
display_name = "Alert DisplayName"
email_subject = "My Test Anomaly Alert"
email_addresses = ["example@test.net"]
}

@rcskosir
Copy link
Contributor

@williamrobinsonlightstream Thank you for taking the time to open this feature request!

Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants