Return app state after "Update All"

Problem/Justification

  • Slow NAS Systems - docker.service has meltdowns if you “Update all” with all apps (or simply have large docker stack setups) trying to be open at the same time

The last 2 months I’ve been using this script → [Script] TrueNAS SCALE App Auto Updater — handles stopped Apps and honestly I was hoping this kind of feature would be integrated natively eventually, even though enterprise machines are.. well.. enterprise-grade. Prices still suck for computer parts though, for those who are adventurous and push their system’s limits.

Impact

  • As everyone who uses the apps catalog is aware, sometimes apps are bulk updated just for codebase changes to the catalog system.
    • As a result, you might complete an entire “Update All” manually at the beginning of the day, then suddenly there is another wave of 30+ bulk updates you’re presented with later in the day. Very frustrating, if you like to not see a sea of yellow on your apps page.
  • Many of us routinely read changelogs for apps (if user selects "return app state" toggle, perhaps have a tool-tip appear to say “updating can introduce breaking changes to your apps, please review relevant release notes before proceeding”
    • Not to mention, with the state of AI/security posturing, it’s usually in best interest these days to stay somewhat on RC, Stable release bleeding-edge.

User Story

I’m hoping that this can be reviewed through a lens besides only benefiting “Slow NAS systems” and from a simple QOL toggle standpoint.

Thank you for taking the time to read this feature request. :)