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

[resource/monitoring_alert_policy] Add support and docs example for MQL Alerting Policy #7464

Comments

@naseemkullah
Copy link

Description

https://cloud.google.com/monitoring/mql/alerts have recently been made available, they can be created in the UI, but have not had luck with terraform

New or Affected Resource(s)

  • google_monitoring_alert_policy

References

https://cloud.google.com/monitoring/mql/alerts

@femnad
Copy link

femnad commented Oct 19, 2020

Added a PR proposing to address this issue.

@naseemkullah naseemkullah changed the title [resource/monitoring_alert_policy] Add support (or example) for MQL Alerting Policy [resource/monitoring_alert_policy] Add support and docs example for MQL Alerting Policy Oct 19, 2020
@yegle
Copy link

yegle commented Oct 29, 2020

It looks like hashicorp/terraform-provider-google-beta#2651 just missed the v3.45.0 cutoff.

What's the release cadence for the beta provider? Thank you!

@nat-henderson
Copy link
Contributor

It should be released next Monday. :)

@ghost
Copy link

ghost commented Nov 28, 2020

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 Nov 28, 2020
@github-actions github-actions bot added service/monitoring-alerting forward/review In review; remove label to forward labels Jan 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.