Nathaniel Caza

I feel like we've had and fixed this bug before; fixing this should include a test for the regression

Waiting for #3779 to merge

@Forfold It's existing behavior untouched by this work. I agree it should be changed but maybe do that in it's own PR since there may be a bit of refactoring...

This will likely come as part of #2639 which is currently in-progress. However, for now, users can add SLACK_DM as an additional contact method from their profile page (escalation policies...

This is a known issue with Postgres on Linux: https://github.com/target/goalert/blob/master/docs/getting-started.md#database > Note: If you are using default install of Postgres on Debian (maybe others) you may run into an issue...

@Forfold That struct is specifically what's going to Postgres -- the idea is to have type/version info embedded in it so we have something to key off of in any...

@Forfold yep, exactly. Not only that, but the `alert.Store` method shouldn't even expose it, it's just to ensure integrity within the store method to the DB (since things change over...

Also, a nice addition would be adding a `metaValue(key: string): string` field to `Alert` in the GraphQL schema. It would play nice with GraphQL, allowing mapping (potentially multiple) metadata fields...

For data storage, it may be better to store as a map so that we leave open the possibility to index these (for search) in the future. Part of validation...

For this, let's plan to implement it at the Service level as an opt-in feature. That way teams can leverage it if they need to for their specific use case....