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

Detectors - Slack notifications inconsistency #470

Open
the-redshift opened this issue Apr 9, 2024 · 0 comments
Open

Detectors - Slack notifications inconsistency #470

the-redshift opened this issue Apr 9, 2024 · 0 comments
Labels

Comments

@the-redshift
Copy link

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?

@atoulme atoulme added the bug label May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants