3 posts tagged with "licensing"

BREAKING CHANGE: The startup arguments for the test runner agent runtime have changed. Testing against production agent runtimes requires a production license.

Opscotch 3.1.6 updates the test runner to exercise the same packaging and licensing path used by current Opscotch deployments.

The test runner now injects configuration through the secrets endpoint, includes production license keys for production test coverage, and can deploy the packager and licenser Opscotch apps into the running Opscotch agent as part of the test flow.

BREAKING CHANGE: Opscotch 3.1.6 removes legacy v1 licensing completely.

3.1.5 was the final release that supported v1 licensing. While the 3.1.5 agent runtime continued to support apps packaged with a legacy license, the remaining hard dependency was in the test runner, which still needed a legacy license to start.

From 3.1.6 onward, legacy v1 licensing is completely removed.

Licensing changed substantially in opscotch 3.1.1.

The licensing model is now hierarchical runtime licensing. Licenses are issued through https://licensing.opscotch.co, can be delegated down a chain of authority, and can be managed without rebuilding packages.

Update for 3.1.6: the previous embedded licensing model has been removed. Use the hierarchical licensing model and the opscotch licensing app for current deployments.