-
Story
-
Resolution: Won't Do
-
Minor
Problem statement
So an instance can itself detect it's not able to update, it would need to know it's not on latest. And endpoint to easily do that from the Evergreen Jenkins plugin, and then surface an Admin Monitor alert, would be good.
Expected
The backend should expose a publicly accessible endpoint returning the current updateLevel.
(Possibly, this would include the channel for it given also it's easy to retrieve from the disk of the instance, and is next to the current updateLevel).
(This would allow the Evergreen Jenkins plugin to consume this easily and display a warning using for example an AdministrativeMonitor to inform users that their instance has the automated upgrade system broken in some way.)
Technical asides
$ docker exec -ti evergreen cat data/updates.json | jq -r .meta.channel general $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.level 188
[JENKINS-57201] [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel
| Epic Link |
New:
|
| Description |
New:
h3. Problem statement To enable h3. Expected The backend should expose a publicly accessible endpoint returning the current updateLevel. (Possibly, this would include the channel for it given also it's easy to retrieve from the disk of the instance, and is next to the current updateLevel). (This would allow the Evergreen Jenkins plugin to consume this easily and display a warning using for example an AdministrativeMonitor to inform users that their instance has the automated upgrade system broken in some way.) h3. Technical asides {noformat} $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.channel general $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.level 188 {noformat} |
| Summary | Original: [Evergreen-backend] Expose a publicly accessible endpoint for the current updateLevel | New: [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel |
| Assignee | Original: Baptiste Mathus [ batmat ] | New: R. Tyler Croy [ rtyler ] |
rtyler in case you missed this. When/if you can do it, would be great. Danke!
| Description |
Original:
h3. Problem statement To enable h3. Expected The backend should expose a publicly accessible endpoint returning the current updateLevel. (Possibly, this would include the channel for it given also it's easy to retrieve from the disk of the instance, and is next to the current updateLevel). (This would allow the Evergreen Jenkins plugin to consume this easily and display a warning using for example an AdministrativeMonitor to inform users that their instance has the automated upgrade system broken in some way.) h3. Technical asides {noformat} $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.channel general $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.level 188 {noformat} |
New:
h3. Problem statement So an instance can itself detect it's not able to update, it would need to know it's not on latest. And endpoint to easily do that from the Evergreen Jenkins plugin, and then surface an Admin Monitor alert, would be good. h3. Expected The backend should expose a publicly accessible endpoint returning the current updateLevel. (Possibly, this would include the channel for it given also it's easy to retrieve from the disk of the instance, and is next to the current updateLevel). (This would allow the Evergreen Jenkins plugin to consume this easily and display a warning using for example an AdministrativeMonitor to inform users that their instance has the automated upgrade system broken in some way.) h3. Technical asides {noformat} $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.channel general $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.level 188 {noformat} |
Billy Bunns
made changes -
| Rank | New: Ranked higher |
| Resolution | New: Won't Do [ 10001 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
rtyler assigned this to you, after a discussion (yeah, soooo long ago :|).