I really want to love the built in notifications for Teams but the management aspect is limiting. Specifically we have a few different teams channels we would like to notify but I cant seem to find a way to name a notification or give a business level description so I can remember/detail which is which. Also the webhook is saved as a protected attribute so we can't reverse look it up. There are a few of us on the team using the workspace so being able to keep the notifications straight is important.
We can work around this by documenting in another tool or giving it 'tag' like 'nametag-<alert specific team>' thats never used in a flow but it seems like a kludge. Am I missing something? How do other folks handle this? Maybe this is actually a feature request to allow for metadata tagging a notification, give it a name + if a webhook metadata for the team + the channel...
11/09/2022, 4:21 PM
Good morning Erin! Yes, this does sound like it would be a helpful feature request. At the moment it does appear that tags are currently what is available for distinguishing notifications. Would you mind opening a GitHub issue here?
11/09/2022, 6:55 PM
Thanks Bianca - I just submitted a feature ticket. Also found a bonus bug in the UI when removing the 1st notification from a notification list and submitted that too.
Yes the tags sort of work, it implies the likely team the notification will go to and we can use that plus the states to maintain a notification decoder in our local documentation for now.
11/10/2022, 9:04 AM
We were struggling with this yesterday too! My thought however was that maybe we should add the creation of notifications (similar to creation of things like blocks) to our CI/CD to some extent. It seems counter-intuitive, but at the end of the day if something happens to our machine, the notifications might be gone as well.
Specifically I believe things like storage blocks/notifications don’t persist when you upgrade Prefect version as well? But I am not certain.