Joaquim Rocha
Joaquim Rocha
This may involve caching results and can be related to #252 . More details TBD.
The current Nebraska's home page and application pages could better display the overall status of updates (which is hopefully that users are looking for). So we need to understand what...
## Current situation Users who are not familiar with how Nebraska works may have a hard way to set up the updates data for a new application as it involves...
## Current situation Nebraska currently lists the apps and, for each app, the groups, and deeper into the abstraction layers. While this is simple, it doesn't constitute a very compelling...
## Current situation We have a REST API but we should make it more accessible for go users, so we can more easily automate common workflows. ## Impact It'll make...
## Current situation We have "Flatcar" and "Other" package types. For Flatcar, no name is needed (since the name is Flatcar itself) and we have a description that's not really...
## Description Currently Nebraska keeps a list of allowed event types and results in the DB. This is coming from the original Coreroller project and it's likely due to restricting...
We want to have a documentation first API that is easier to maintain and understand. The plan involves oapi-codegen and echo to generate client and server stubs. **Acceptance criteria:** -...
I have been working on this PR to make the group's stats a bit more accurate to what the user perceives: the issue is that we are gathering any instances...
## Current situation Right now only the update time outs seem to be considered for the safe-mode enablement. ## Impact If there are errors but no time outs, the updates...