DeveloperModuleLoadingServlet

Module Development
1

For my module development, I am using a mixture of the Ignition Maven Plugin and the Gradle Module Plugin. I know there are tasks there to deploy to a Gateway running in "Development" mode. The issue that I am running into is that I have a "license" html file that is provided with my modules. When I try to upload to the DeveloperModuleLoadingServlet I have an error thrown

Cannot start up module "com.mycompany.namespace", it doesn't exist.

Around there, I see;

Moving module mymodulename to quarantine because license not yet accepted.

Is there a way to auto accept the license through this servlet?

@Kevin.Herron and @PerryAJ it looks like you wrote the original code for this so maybe you have an idea. Im not seeing anything obvious looking at ignition-maven-plugin/src/main/java/com/inductiveautomation/ignitionsdk/PostModuleMojo.java at 71f4d87649edf7f97e0e16fa373a41b1987680df · inductiveautomation/ignition-maven-plugin · GitHub or ignition-module-tools/gradle-module-plugin/src/main/kotlin/io/ia/sdk/gradle/modl/task/Deploy.kt at 4fd236ab99605f165c610000eae27b3d13e60f92 · inductiveautomation/ignition-module-tools · GitHub

2

Install it once manually, accept the certificate, then use the action to automatically update it as you make changes.

3

Is it safe to assume that they use the EULAS table to store the accepted license file? The CRC value in this table looks to be a normal crc-32 value of the license file. Im looking to preconfigure the environment more. My license file tends to not change too often.

4

Yeah, the IDB is the 'source of truth' for this stuff (in 8.1, there are some differences in 8.3).

You could:

  1. Start from a clean system, take a .gwbk
  2. Install your module manually and accept the cert, take a .gwbk
  3. Run sqldiff to compare the IDB files between the two.
1 Like