Add Capabilities Framework#84
Conversation
Update commissioning, readiness, and module selection for Ignition 8.3. Parse third-party module descriptors so unsigned modules and gateway dependencies can be enabled automatically, and use Testcontainers 2 for compatibility with current Docker engines.
implement a capability/profile based structure
|
@kevinherron, wanna check this out? This is the best way I could think to model the differences between It's wayyy more work than other Testcontainers wrappers usually do; however, other Testcontainers wrappers are not concerned with wrapping multiple disparate container versions. I know I'm missing your 3rd Party Module certificate/license acceptance code, let me know if anything else seems to be missing. |
|
This seems reasonable, I'll install it locally to test once you get the 3rd party module support added - that's where I'm using this right now. Better than throwing away 8.1 support like I was doing :) |
Combine Capabilities+Appliers, add 8.3 third party module support. Fix module.xml parsing force line endings force spotless format version
671f57f to
2bd2620
Compare
|
@kevinherron 3rd party module support is now working for 8.3. It is supported in 8.1, but isn't currently tested for (since there's no great way to automatically accept the license + cert, and I don't really want to mess with a dedicated gateway backup for that test). |
2 participants
Summary
Adds capability-based compatibility handling for Ignition Docker images.
Each Ignition profile now defines which capabilities are supported, when they became available, and how they map to Docker configuration. Unsupported or early-version capabilities generate warnings instead of failing.
Also includes expanded tests for capability declarations, version thresholds, warning behavior, profile translation, and container configuration.