You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenWISP Controller has recently introduced the concept of Groups. It would be great to allow to upgrade all the devices related to a group with a mass upgrade operation. We could add an optional group field on the mass upgrade model which if filled would cause the upgrade operation to work only on the devices related to that group.
There would be a few things to change to make sure the dry run method works consistently. In the admin we have to show the group field as an autocomplete field and add a filter by group (also autocomplete) in the admin list.
The internal logic of models and methods shall also take into account this change and if the group is defined only devices of that group must be upgraded.
OpenWISP Controller has recently introduced the concept of Groups. It would be great to allow to upgrade all the devices related to a group with a mass upgrade operation. We could add an optional group field on the mass upgrade model which if filled would cause the upgrade operation to work only on the devices related to that group.
There would be a few things to change to make sure the dry run method works consistently. In the admin we have to show the group field as an autocomplete field and add a filter by group (also autocomplete) in the admin list.
The internal logic of models and methods shall also take into account this change and if the group is defined only devices of that group must be upgraded.
We will add to add validation logic in the model to ensure that the group of a mass upgrade operation matches its organization, there's already plenty of similar logic in different openwisp modules, see also: https://github.com/openwisp/openwisp-users/blob/master/openwisp_users/mixins.py#L11 .
We must remember to not forget to add mention of this feature in the README (intro and mass upgrade explanation section).
The text was updated successfully, but these errors were encountered: