App configuration not updating

Questions / Help
1

I’ve updated my fly.toml repeatedly and tried redeploying the app. The deployments are successful but the configuration isn’t actually updating… I’ve verified the fly.toml is valid using flyctl config validate. After each deployment, fly config show still shows the old config.

2

Hi… flyctl is unfortunately overly permissive about certain kinds of configuration-file errors (e.g., keys in the wrong location).

Could you post your full fly.toml—and indicate the part that isn’t getting recognized?

(Feel free to * out any app names, env-var values, etc.)

3

Sure, thanks. Here’s the config:

app = '****'
primary_region = '***'

[build]

[http_service]
#  internal_port = 3000
  force_https = true
  auto_stop_machines = "off"
  auto_start_machines = false
  min_machines_running = 2
  processes = ['app']

[[vm]]
  cpu_kind = 'shared'
  cpus = 2
  memory_mb = 2048

[[restart]]
  policy = 'on-failure'
  retries = 10
  processes = ["app"]

I changed auto_stop_machines to “off” but it’s not updating.

4

hi @jchiatt

The changed setting is going to show up as

  auto_stop_machines = false

in your config (when you run fly config show), which is equivalent to "off".

5

Ah I didn’t know that. That makes sense now. Thanks!