Open bajaj-gaurav opened 3 years ago
The id field is what identifies the alert. The system assigns each new alert a unique id which identifies that alert for its lifetime. Users of terraform cannot set or change the id field of an alert. As for the other fields, the first step is to change the go wavefront API to support those fields. Once a new version of the go wavefront API is released that supports those fields, then it will be possible to change the terraform plugin to support the same fields.
Note that many other fields of Alert besides id are set by the system and are read-only.
For example processRateMinutes seems to be read-only.
Do we have an ETA on when we are planning to support the following arguements for wavefront_alert(Resource : wavefront_alert) via terraform:
id creatorId evaluateRealTimeData secureMetricSDetails snoozed processRateMinutes includeObseleteMetrics
In the doc, https://registry.terraform.io/providers/vmware/wavefront/latest/docs/resources/alert, can't see the above field.
Also, if not planning to support the above field soon then do we have an alternative by which in addition to the arguements supported by the terraform, we can have the above fields as well while creating the alert.