terraform-provider-google: Slack Notification Channel creation via terraform no longer works

I think I found a workaround for this if you want to define it all in terraform:

resource "google_monitoring_notification_channel" "website_slack_alerts" {
  project      = "project123"
  display_name = "Slack Staging Website Alerts Channel"
  enabled      = "true"
  type         = "slack"
  labels = {
    "channel_name" = "#test-channel"
  }
  sensitive_labels {
    auth_token = data.google_secret_manager_secret_version.slack_bot_user_oauth_token.secret_data
  }

  depends_on = [ 
    google_secret_manager_secret.bot_secret
  ]
}

data "google_secret_manager_secret_version" "slack_bot_user_oauth_token" {
  secret  = "staging-website-slack-notifications-bot-token"
  project = "project123"

  depends_on = [ 
    google_secret_manager_secret.bot_secret
  ]
}

# This creates the secret, but not the data.  Add it manually.  
# The apply will fail till this is added because website_slack_alerts can't get the secret version!
# You could use secret_manager_secret_version if you wanted the secret in code too.
# This will be the token that starts with "xoxb"
resource "google_secret_manager_secret" "bot_secret" {
  project   = "project123"
  secret_id = "staging-website-slack-notifications-bot-token"

  replication {
    automatic = true
  }
}

On the slack side, I created the app, and added the channel.join and chat.write permissions. I also manually installed it in the channel I was targeting after installing it to the workspace. The token is the Bot User OAuth Token from the OAuth and Permissions section.

I’m using version 4.46.0 of the provider.

Hope this helps!

Running into the same problem. As described by @johan-torres-data, the team field seems to be missing. When inspecting requests sent by gcp’s to Slack’s API I see that it tries to send, next to the auth_token and channel_name; the team name. These are valid API labels, but for some reason Terraform doesn’t accept team during configuration.

Hi everyone, same issue here, I tried to create the channel using terraform but it didn’t work, so I created another one from the UI and that one works, the only difference that I noticed is one field called team that in my case is the Slack-workspace name, that label is not available within the “google_monitoring_notification_channel” resource. Each time that I want to set up a new channel Slack asks me to allow Monitoring to have some permissions, not pretty sure if could be related with that. In the next picture, you can see that the first has a team label, that was created by the UI the second one uses terraform.

We actually got in touch with responsible team and this is what I heard back

The long term goal is to have full TF parity with console/cli. Lots of working being done at the moment. I have +1 the ticket and will be booking a follow up meeting with the PM to discuss progress

So I hope sometime in near future we would get this done.

Any update regarding this issue? As mentionned above the only solution in order to use the slack channel for me was to copy past in my alert resource the channel name that can be found with the following command:

gcloud beta monitoring channels list

Can concur here around the Team not being included. Current workaround is super ugly but essentially create the slack alert manually and copy down the notification channel ID which is something like:
"projects/<gcp_project_id>/notificationChannel/<NotificationchannelID>" Also frustrating that you can’t just pass the notification channel name. This “workaround” at the very least gives your created Alerts a working channel to reference in environments that will be stable for a while.

Yeah, the issue is resolved after it’s reported internally as well! We should be good at using the following:

                    labels={
                        "channel_name": <slack channel>,
                        "team": "<team name>",
                    },

Have migrated my workaround to the above in May this year which is working perfectly fine

Another possible (albeit terrifying workaround) is to use slacks feature to send emails to a channel:

1. Rightclick the channel in slack
2. View Channel Details
3. Integrations
4. Send Email to this channel
5. Use the provided email with a email notification channel that can be configured through terraform

It’s not pretty but it works.