Update Alertmanager models

[gotjosh]

Update the Alertmanager models to add necessary ones for the /alerts and /alerts/groups endpoints.

[gotjosh]

I genuinely will never understand go mod. The difference in dependencies is produced by running go mod tidy and then go mod vendor.

I'm not sure if it's because I have a different set of dependencies or because we forgot to converge at some other point - any pointers?

[codesome]

No idea about the go mod changes, but would not worry about it looking at it

[codesome]

This is the first time I am seeing type x = y syntax 😱 how does it work?

[codesome]

Is it equivalent to type x y?

[gotjosh]

I can't find the original article I read on the subject which does a better job at explaining than I do, but it is different. The tl;dr is that type x y is a type definition, in the eyes of the compiler is a new type just like type X struct { y } whereas type x = y is type alias which means is just a different name for the same type (and thus would have the same memory footprint).

In practical terms, this allows us to use our types and the returned AM types interchangeably w/o having to do any type casting. We are not operating on these types so it makes sense.

[papagian]

The modifications LGTM
I don't know about the go dependencies but I get the same result if run go mod tidy in master.
Can you please post also the update spec.json and post.json?

[gotjosh]

@papagian on a closer inspection, I found a couple more inconsistencies with the upstream API could I please get another look?

[papagian]

Does this mean that the query parameter will become filter instead of Filter in this request, right?

[gotjosh]

Yep! I have already fixed this with https://github.com/grafana/grafana/pull/32604/files

[papagian]

For reference, these changes are required for conformance with this API route