Linoy Zaga

Results 11 comments of Linoy Zaga

Hi @huzie , @mbazhlekova is correct. Slack requires interactive authentication through OAuth, therefore Slack destinations can only be imported to terraform after creating through the UI. Slack channels can be...

@gdubroeucq You can get the Slack channel id from this NerdGraph [query](https://api.newrelic.com/graphiql?#query=%7B%0A%20%20currentUser%20%7B%0A%20%20%20%20account%28id%3A%201705020%29%20%7B%0A%20%20%20%20%20%20aiNotifications%20%7B%0A%20%20%20%20%20%20%20%20channels%20%7B%0A%20%20%20%20%20%20%20%20%20%20entities%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20id%0A%20%20%20%20%20%20%20%20%20%20%20%20name%0A%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D%0A). You can add filters as you wish, like the channel name etc. Also, if you imported the destination...

Hi everyone, The `auth_basic` issue is fixed in the [latest version](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs) (3.8.0).

Hi @alisson276 , Thank you for your feedback and we'll address this issue. In the meanwhile, you can add the following code to your imported Slack destination resource: ``` lifecycle...

Hi everyone, The token in `auth_token` attribute doesn't return from our API, because it’s sensitive data. After deeper investigation, `ignore_changes` is the only way to avoid this issue (as mentioned...

Hi everyone, We are working on creating destinations as data sources as well.

Hi @MAN98 , We are working on that right now. Hopefully, next week you'll see it in the next version of the provider. I'll update here as well.

Hi @cdobbyn , The data source for notifications destination is on our roadmap plan for this/next Q. You are more than welcome to submit a feature request to track this...

Notifications destination is available in the latest version of the New Relic [provider](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs). Closing this issue.