[bug]: Existing local clusters fail due to docker-compose format changes in axon-dash configuration

[millerjp]

See #923

Recent security updates to axon-server,axon-dash and axon-agent packages for Debian and RPM removed write permissions to /etc/axonops/. The Debian and RPM packages are installed by the docker pipelines that build the containers that are used in AxonOps Workbench local clusters. The changes are breaking existing local clusters that rely on the legacy command: sed ... in docker-compose files. Newly created local clusters create axon-dash successfully , but older deployments fail to load the axon-dash tab due to permission errors.

Root Cause:

Old format: command:

    command: >
      /bin/sh -c "sed -i 's|private_endpoints.*|private_endpoints:
      http://axon-server:8080|' /etc/axonops/axon-dash.yml &&
      /usr/share/axonops/axon-dash --appimage-extract-and-run"

New format: Uses environment:

    environment:
      - AXONSERVER_PRIVATE_ENDPOINTS=http://axon-server:8080

Existing docker-compose.yml files retain the old command structure, which now fails due to write restrictions.

Impact:

Users with pre-existing local clusters cannot access the monitoring dashboard (axonops-dash).

Proposed Fix:

Add automatic migration in the Workbench Electron app to:

Detect legacy command: sed ... patterns in docker-compose.yml.

Replace with new environment configuration.

Ensure backward compatibility by modifying files at when users try to launch them