I'm seeing issues upgrading modules with 8.3.
To reproduce:
Create a gateway (8.3.0 b2025091510) using Docker.
Install module version 0.2.1.
Reboot using the Web UI.
View modules in the Web UI, and see that 0.2.1 is installed.
Install module version 0.2.2.
Reboot using the Web UI.
View modules in the Web UI, and see that 0.2.1 is still installed.
I'm not seeing any errors or warnings in the logs.
In order to get the upgrade to happen, I have to uninstall 0.2.1, reboot, install 0.2.2, the reboot again.
Modules attached:Embr-SNMP-Ignition83-0.2.1.modl (2.3 MB)Embr-SNMP-Ignition83-0.2.2.modl (2.3 MB)
There's currently an issue when upgrading modules that have different file names.
IGN-14211 for reference, targeted for Ignition 8.3.2.
2 Likes
Lame, but glad it's understood.
Personal complaint: the current feedback loop for testing 8.3 modules is very slow gradle-module-plugin to support some API actions (i.e. upload a module/modules + restart)?
I don't think anything is currently planned but it doesn't hurt to ask.
We don't use the Maven or Gradle plugins so the incentives aren't exactly aligned when it comes to improving the dev experience using them.
Gotcha, created an issue here:
opened 02:22AM - 08 Oct 25 UTC
## Problem
With the removal of module hot-loading and the module loading servlet… , the current developer experience for module's targeting `8.3` is poor.
The feedback time between making changes/compiling, manually uploading, and manually restarting the gateway is very long.
## Suggestion
The new `8.3` REST API allows for loading modules and restarting the Gateway.
I suggest that the `gradle-module-plugin` be updated with a new `8.3` specific `Deploy` task to:
1. Upload a module.
2. Restart the Gateway.
This would bring things back to feature parity with the `8.1` developer experience.
I think it's just a reworking of the Deploy task to target the new API.
