Support for fly.yaml

Questions / Help
1

Is there any interest from the fly.io team to support fly.yaml as an alternative (/fallback) mean of feeding config into flyctl?

I.e. a classic generated skeleton can be translated as

app: xxx
processes: []
env: {}
experimental:
  allowed_public_ports: []
  auto_rollback: true
services:
  - http_checks: []
    internal_port: 8404
    processes:
      - app
    protocol: tcp
    script_checks: []
    ports:
      - force_https: true
        handlers:
          - http
        port: 80
      - handlers:
          - tls
          - http
        port: 8404
    tcp_checks:
      - grace_period: 1s
        interval: 15s
        restart_limit: 0
        timeout: 2s

It is possible to use work arounds like

cat fly.toml | yj -ty  > fly.yaml
cat fly.yaml| yj -yt > fly.toml

but a native support would be much better.

If there is an interest, I can work on the PR.

Cheers

1 Like