This is mostly found by comparing to GNOME firmware. I see that firmware-updater doesn't have any method to force a metadata refresh cycle.
GNOME Firmware:
For the MAJORITY of users, this doesn't matter because fwupd-refresh.service will refresh metadata ~ once per day. But there are two cases that it makes sense to have a manual button.
For an end user who is "offline" when fwupd-refresh.service ran or on a limited network when it run so they didn't get updated metadata. They need a way to manually trigger a metadata refresh.
For developers who are uploading firmware to LVFS and doing end to end testing it's going to be problematic to be able to validate their firmware update worked properly without resorting to command line tools and manually running fwupmdgr refresh --force. Note: this ties in VERY heavily to https://github.com/canonical/firmware-updater/issues/274. If that isn't fixed then it will make it very difficult to use firmware-updater for development purposes.
This is mostly found by comparing to GNOME firmware. I see that
firmware-updaterdoesn't have any method to force a metadata refresh cycle.GNOME Firmware:
For the MAJORITY of users, this doesn't matter because
fwupd-refresh.servicewill refresh metadata ~ once per day. But there are two cases that it makes sense to have a manual button.fwupd-refresh.serviceran or on a limited network when it run so they didn't get updated metadata. They need a way to manually trigger a metadata refresh.fwupmdgr refresh --force. Note: this ties in VERY heavily to https://github.com/canonical/firmware-updater/issues/274. If that isn't fixed then it will make it very difficult to use firmware-updater for development purposes.