Reset docker compose override file

[firyx]

PULL REQUEST

Overview

Currently docker-compose.override.yml data are read, updated (with sia, accounts versions) and saved back, i.e. the override data are preserved, during deploys.

As discussed and planned this PR regenerates docker-compose.override.yml file freshly, i.e. existing override data are cleaned, they are not preserved anymore.

Example for Visual Changes

Checklist

• [x] All git commits are signed. (REQUIRED)
• [x] All new methods or updated methods have clear docstrings.
• [x] Testing added or updated for new methods.
• [x] Verified if any changes impact the WebPortal Health Checks.
• [x] Appropriate documentation updated.
• [x] Changelog file created.

Issues Closed

[linear[bot]]

SKY-136 Reset docker compose override file

ansible should be completely resetting the docker override right now it reads the file, this should be removed if there are custom configs in the override file, they should be there for testing, and deploy will reset it, or they should be defined in a config file somewhere. The second case being how portal operators would handle custom services.

[MSevey]

This is going to nuke the override on dev3 with gundb relay but I guess that fine?

version: "3.7"

services:
  sia:
    build:
      args:
        branch: chris/fix-lazy-pinning

  gundb-relay:
    container_name: gundb-relay
    env_file:
    - .env
    environment:
    - DEBUG=true
    - PORTAL=http://${SERVER_DOMAIN}
    image: skynetlabs/gundb-relay
    networks:
      shared:
        ipv4_address: 10.10.10.163
    ports:
    - 8765:8765
    restart: unless-stopped

yea that is fine, we dropped the gundb work for now