Scale - custom App YAML save doesn't seem to work correctly

TrueNAS General
,
1

I have a currently running YAML file. Apps are up and running. I’m making changes to it, hitting save. No error message and stack restarts. But when I come back the YAML is not what I saved - in fact it has significant reformatting.

An example:


networks:
  scaledocker:
    external: true

services:
  # Heimdall Service
  heimdall:
    container_name: heimdall
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/New_York
    image: lscr.io/linuxserver/heimdall:latest
    networks:
      - scaledocker
    ports:
      - '81:80'
      - '444:443'
    restart: unless-stopped
    volumes:
      - /mnt/m2/docker_configs/heimdall:/config

  ##########################################################
  # Below are VPN-connected containers using Gluetun
  ##########################################################

  # Prowlarr Service
  prowlarr:
    image: lscr.io/linuxserver/prowlarr:latest
    container_name: prowlarr
    network_mode: "container:gluetun"  # Use Gluetun's network stack
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/New_York
    volumes:
      - /mnt/m2/docker_configs/prowlarr:/config
    restart: unless-stopped

After I save I have this:

networks:
  scaledocker:
    external: True
services:
  heimdall:
    container_name: heimdall
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/New_York
    image: lscr.io/linuxserver/heimdall:latest
    networks:
      - scaledocker
    ports:
      - '81:80'
      - '444:443'
    restart: unless-stopped
    volumes:
      - /mnt/m2/docker_configs/heimdall:/config
  prowlarr:
    container_name: prowlarr
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/New_York
    image: lscr.io/linuxserver/prowlarr:latest
    network_mode: container:gluetun
    restart: unless-stopped
    volumes:
      - /mnt/m2/docker_configs/prowlarr:/config`
 ``

Is this expected behavior?  Not only is it deleting comment sections and rearranging my file, it's making mistakes (capitalizing True for example).

Any help appreciated.
2

Obviously, we focus on functional operation.

If reformatting is an issue, then I’d suggest a Feature Request. In the meantime, I assume you could edit YAML externally and then import?

If capitalizing “true” or any other change has an impact on functional behaviour, its likely a bug. Please document and report that.

24.10.1 has some bug fixes in the YAML area, but nothing I can see that might specifically address this issue.

3

That’s what I did - I formatted it externally. I composed it in yamllint and then copied it into scale.

The reason I bought up the change in case is that when troubleshooting using ChatGPT it constantly tells me the capital is incorrect and may cause errors. The fact that it changes it just seems strange.

but the fact that it removes comments and moves things around in the YAML file seems quite bizarre actually. I guess I’m just trying to understand what format changes are enabled. Somebody had to code that into being - is there a reference for what changes to YAML files will be made upon upload?

Thank you very much for the reply. I honestly was losing my mind for awhile thinking I had uploaded the wrong yaml when I kept saving it it kept not looking like the one I uploaded.

4

Its a brand new feature… its really experimental in this version as it was included late in the release cycle.

You can help remove the rough edges with Feature requests or bug reports.
Is everything working as expected despite the formatting?

5

Someone here nearly lost his entire pool to “troubleshooting using ChatGPT”. Just saying… :scream:

1 Like