v0.6

Release Notes

0.6.0

Consumer

• Address some gaps found in the decoupling work
• Addition of the Vector agent
• Added a browser-driven container regression for UI-requested shutdown across all six built-in consumer types, including provider disconnect and process-exit evidence.
• Fixed built-in custom command discovery for consumers without an agent-specific handler directory, allowing the shared shutdown handler to be advertised and executed.
• Fixed Fluentd monitor endpoint discovery so a local bind address no longer replaces the remote OpAMP provider hostname.

Client Config Generator Service

• Added an independently packaged, schema-driven server plugin and standalone UI for generating Supervisor and Observer consumer configurations.
• Added versioned list, load, validate, and atomic-save API controls with configured-directory containment and read-only deployment support.
• Added provider deployment discovery, build/version registration, static help, documentation, and container validation for enabled and disabled deployments.

CLI

• Improvements around the CLI to clean up log files
• make it easier to startup demos
• base configuration enhanced to provide additional demo scenarios
• Added cli-config commands to view, summarize, and safely switch the active CLI demo profile configuration, with autocomplete support and friendlier interactive error messages.
• Fixed Broker startup from the CLI and source-tree command line by ensuring repo-level shared modules are importable.
• Improved background startup failures so Broker and other managed processes report a useful log detail alongside the exit code and log path.
• Added developer CLI commands to clean labelled Docker or Podman regression images and optionally include legacy opamp-* images.
• Added release wheel publishing from local, AWS, or Azure origins into GitHub, with automatic discovery of the newest retained AWS bucket, cloud deployment artifact fallbacks, and a separate push-to-cloud command for local-to-cloud transfers.
• Updated the full repository security gate to use pytest importlib mode so duplicate test filenames in component-specific test directories collect independently.

Cloud Deployments

• Added equivalent two-VM regression and demonstration environments for AWS CloudFormation and Azure Resource Manager, including networking, restricted administrative access, OpAMP server and consumer roles, Keycloak, OAuth2 Proxy, Nginx, and OpenTelemetry Collectors.
• Added Bash and Windows PowerShell deployment, teardown, and artifact-packaging commands, plus GitHub Actions cloud deployments using OIDC credentials without external marketplace actions.
• Added automatic Python wheel packaging and Linux bootstrap staging, including cross-platform UTF-8 and LF normalization for scripts and wheel manifests produced on Windows.
• Added optional AWS EC2 key-pair creation with protected local PEM storage, existing-key inference from PEM filenames, automatic administrator CIDR detection, and regional key validation.
• Added timestamped retained S3 and Azure Blob storage outside the ordinary infrastructure teardown boundary, with private regression-result retention, single-target storage cleanup, and --all cleanup for generated OpAMP retention storage.
• Updated retained deployment and regression result folder names to use hyphen-separated UTC timestamps such as yyyy-mm-dd-hh-mm-ss without creating a nested date path hierarchy.
• Normalized agent-shutdown container evidence permissions before container removal so AWS retained-result uploads do not skip restrictive Elastic Heartbeat output files and exit with status 2.
• Added generated Markdown connection guides containing service URLs and ready-to-run SSH commands, retained locally and in cloud storage alongside provider deployment outputs.
• Added a provider-neutral regression command that runs selected test sets and uploads complete local evidence, including failed-run status manifests, to retained AWS or Azure storage.
• Added an Azure, AWS, or build-only deployment selector to the main GitHub Actions workflow, controlled by the CLOUD_PROVIDER repository variable or a manual-run override. Pushes to main default to AWS, deploy the CloudFormation regression environment, run retained regression evidence upload, and fail the workflow when regression fails.
• Added a provider-aware GitHub OIDC setup helper that creates or updates the AWS IAM role or Azure Microsoft Entra application, configures branch-scoped GitHub federated credentials, and can write repository secrets and variables through the GitHub REST API.
• Added application-aware deployment completion and diagnostics: AWS wait conditions report VM bootstrap failures, server installer and startup logs are retained, and Keycloak readiness is checked before realm configuration.
• Added cloud regression troubleshooting notes covering GitHub action policy limits, OIDC setup gaps, mounted-checkout Git ownership checks, Windows-to-Linux line endings, consumer plugin import cycles, ST scenario evidence, and Playwright image/version drift.
• Improved the AWS regression workflow failure message so a passing regression pack followed by retained evidence upload failure is reported as an upload problem, with the local upload manifest printed in the job log.
• Added deployment cost guidance, cleanup instructions, safe-rerun behavior, provider terminology, resource ownership, and failure recovery documentation in the cloud operator guide, AWS guide, and Azure guide.

Full Changelog: v0.5...v0.6

v0.5 Enhancements

Lots of features and development work - see https://blog.mp3monster.org/2026/06/14/opamp-implementation-update/

0.4 Enhancements

Full Changelog: v0.3...0.4

The changes have focussed on building out capabilities such as:

• HTTPS support
• Manual Agent Approval
• Enhanced docs
• Making the custom commands completely extensible
• Basic support for Bearer Tokens (no OpAMP client-server negotiation on its use yet)

Refactor to support Fluentd as well

This version of the OpAMP solution introduces supervisor support for Fluentd in addition to Fluent Bit. At this point testing has been limited with Fluentd.
This has meant refactoring the code.
We also have in place logic for bearer tokens for the UI, with a development mode which disables the checking. This functionality has not yet been tested.

v0.2

The development has introduced a lot of functionality:

• AgentToServer functionality has developed with new parts of the API implemented
• UI enhanced to provide more direct control
• command framework refined
• Checks on message ordering added

v0.1

initial release of code