You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Assume I have detector. . Then I want to configure it with Slack Notifications - so I choose my channel from the list (note - all channels on the drop down list are prefixed with #).
Next, I perform an API Call [GET] to check that detector definitions. Within notification section, I will have channel name, prefixed with #. The same behavior occurs when using terraform import + terraform show. So far so good.
Then, if I wanted to create terraform resource using the information obtained in aforementioned way, I'll have to drop that # prefix, because it is enforced by validation:
errs=append(errs, fmt.Errorf("Please exclude the # from channel names in %q", parts[2]))
Furthermore, when terraform apply is performed, it will actually overwrite the channel name in the notification so it has no prefix. Something like this is not possible via UI.
So could somebody elaborate on the reason why is that inconsistency present?
The text was updated successfully, but these errors were encountered:
Hi,
Assume I have detector. . Then I want to configure it with Slack Notifications - so I choose my channel from the list (note - all channels on the drop down list are prefixed with
#
).Next, I perform an API Call [GET] to check that detector definitions. Within notification section, I will have channel name, prefixed with
#
. The same behavior occurs when usingterraform import
+terraform show
. So far so good.Then, if I wanted to create terraform resource using the information obtained in aforementioned way, I'll have to drop that
#
prefix, because it is enforced by validation:terraform-provider-signalfx/signalfx/notifications.go
Line 196 in 49e6ad8
Furthermore, when
terraform apply
is performed, it will actually overwrite the channel name in the notification so it has no prefix. Something like this is not possible via UI.So could somebody elaborate on the reason why is that inconsistency present?
The text was updated successfully, but these errors were encountered: