While the original functionality didn't call for this specifically, it has become apparent that over time there will be a need to update the packages on the host machines. It's not clear how or where this logic makes the most sense, but essentially, when a user updates the nanoagents from within the dashboard, we also want to to update the packages if anything is out of date. So, we'll need to add this logic to either:
1 - The current nanoagent-update script.
2 - The bootstrap script
3 - A separate script altogether that gets called separately on update.
While the original functionality didn't call for this specifically, it has become apparent that over time there will be a need to update the packages on the host machines. It's not clear how or where this logic makes the most sense, but essentially, when a user updates the nanoagents from within the dashboard, we also want to to update the packages if anything is out of date. So, we'll need to add this logic to either:
1 - The current nanoagent-update script. 2 - The bootstrap script 3 - A separate script altogether that gets called separately on update.
@glinton, @notxarb thoughts or preferences?