[ui] Adding canary_tags the web UI

[philrenaud]

Appending, with a custom style, to anyplace we show service tags:

Resolves #13018

[github-actions]

Ember Asset Size action

As of b2d7c3c

Files that got Bigger 🚨:

File	raw	gzip
nomad-ui.js	+209 B	+46 B
nomad-ui.css	+174 B	+53 B

Files that stayed the same size 🤷‍:

File	raw	gzip
vendor.js	0 B	0 B
vendor.css	0 B	0 B

[github-actions]

Ember Test Audit comparison

	main	b2d7c3c	change
passes	1435	1435	0
failures	0	1	+1
flaky	0	0	0
duration	10m 18s 779ms	000ms	-10m 18s 779ms

[philrenaud]

Fun CSS trick to add copy to an element without adding it in the template itself.

[philrenaud]

Rather than make these their own conditional table column, decided to append them to the end of the rest of the tags on a service, should they exist.

[lgfa29]

Minor comments, but LGTM.

I wonder if it would be possible to apply the correct set of tags instead of always displaying them all depending on the allocation deployment status:

$ nomad operator api /v1/allocations | jq '.[].DeploymentStatus'
{
  "Canary": false,
  "Healthy": true,
  "ModifyIndex": 24,
  "Timestamp": "2022-12-05T15:32:23.764038-03:00"
}
{
  "Canary": true,
  "Healthy": true,
  "ModifyIndex": 35,
  "Timestamp": "2022-12-05T15:33:13.774562-03:00"
}

So the canary_tags would only show for canary allocs, and the tags would show for non-canary.

[philrenaud]

I wonder if it would be possible to apply the correct set of tags instead of always displaying them all depending on the allocation deployment status:

@lgfa29 I was thinking about this, but figured it might be worthwhile to say something like "... and if this alloc is ever in a canary state, these are the tags it would have", as the canary state might be short-lived and fleeting.

[lgfa29]

as the canary state might be short-lived and fleeting.

I think the use of canary_tags is usually associated with manual promotion after validating the changes are correct, so I would imagine they are not as short-lived. But it would be a big lift to parse that API response, so just something to maybe consider in the future 👍

[github-actions]

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.