Skip to content

sysdig_monitor_notification_channel_email - optional share_with_current_team #612

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

Closed
bashbang opened this issue Mar 19, 2025 · 2 comments
Closed
Assignees

Comments

@bashbang
Copy link
Contributor

The current default behaviour of the share_with_current_team = false in sysdig_monitor_notification_channel_email returns a 403 error when not a site admin (eg: if a Team Manager doesn't set share_with_current_team = true an error is returned:

[ERROR] vertex "sysdig_monitor_notification_channel_email.tf_sre" error: 403 Forbidden

This could very well be the default upstream behaviour on the Sysdig side which is not a Terraform issue, however I was unable to find any documentation or reference to this issue. I was able to get it solved with support from @bashfulrobot.

I'd suggest:

  • If this is a Sysdig default, an upstream ticket be opened to either invert this setting or make it non-optional
  • Update the TF default to be the invert or a non-optional feature.
  • Update the docs to indicate this possible issue (I would have done a PR but wasn't able to find the GH code for the docs)
  • All of the above.

At worse case this ticket left behind for posterity in the hope that others can benefit from searching and finding this ticket.

@bashbang
Copy link
Contributor Author

Found docs...made PR#613. Wasn't able to link them. Sorry about that.

@dbonf
Copy link
Collaborator

dbonf commented Mar 20, 2025

thanks for rising this issue!

The default is like that for retro-compatibility because the share_with_current_team argument was added later to the resource, that is also the reason we cannot change it, but we can make the doc clearer as you suggested.

@dbonf dbonf self-assigned this Mar 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants