Provisioning & Testing
This page provides a first overview of the Provisioning workflows available for Controller configuration and testing.
Provisioning workflows can support:
- Factory configuration
- Factory testing
- Spare part Controller preparation
If your main goal is | You may prefer | Because | High-level purpose | Tradeoffs |
|---|---|---|---|---|
| # Fast direct per-unit configuration | SSH | Lowest overhead, direct persistency/file control | Direct access to the Controller, allowing for configuration, reboot, and configuration via config files | No guardrails, more control, more responsibility |
| # Manual configuration through the device interface | Config UI | Configuration is done through the existing device interface | Configuration through the device interface | No automation |
| # Offline file-based configuration | USB stick | Configuration can be applied without network access | Offline file-based configuration | Not very flexible but quick to implement |
| # Structured configuration, testing, and validation | Test Adapter | Built for repeatable configuration, test execution, and validation flows | Repeatable configuration and production test execution | Comes with decent overhead but great for large-scale provisioning. Often combined with SSH |
| # Full production flow (configure + verify) | SSH + Test Adapter | SSH for direct access, Test Adapter for repeatable configuration and testing | Direct configuration and repeatable configuration and production test execution | Combines the flexibility of SSH with the configuration and test structure of Test Adapter |