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
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:
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.
The text was updated successfully, but these errors were encountered:
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.
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:
At worse case this ticket left behind for posterity in the hope that others can benefit from searching and finding this ticket.
The text was updated successfully, but these errors were encountered: