# flyctl deploy does not honour all entries in config for machine apps

**URL:** <https://community.fly.io/t/flyctl-deploy-does-not-honour-all-entries-in-config-for-machine-apps/7269>\
**Category:** Questions / Help\
**Created:** [September 19, 2022, 7:58pm UTC](https://community.fly.io/t/flyctl-deploy-does-not-honour-all-entries-in-config-for-machine-apps/7269 "2022-09-19T19:58:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ignoramous](https://avatars.discourse-cdn.com/v4/letter/i/a9adbd/32.png) [@ignoramous](https://community.fly.io/u/ignoramous)\
**Post date:** [September 19, 2022, 7:58pm UTC](https://community.fly.io/t/flyctl-deploy-does-not-honour-all-entries-in-config-for-machine-apps/7269/1 "2022-09-19T19:58:04Z")

</div>

I recently deployed `udns`, a Machine app, [with `flyctl`](https://community.fly.io/t/preview-deploying-applications-on-machines-with-flyctl/6171) to all available Fly regions, and found that, one VM is spun-up per connection instead of the connection being sent to an already alive VM.

The Machine app’s [`services` section](https://github.com/serverless-dns/serverless-dns/blob/693f54517/fly.machines.toml) contains:

```auto
[[services]]
internal_port = 8080
protocol = "tcp"

  [services.concurrency]
  hard_limit = 75
  soft_limit = 60
  type = "connections"

```

But when I fetch config for the app, it shows:

```auto
$ fly config display -a udns
...
    "services": [
        {
            "concurrency": {
                "hard_limit": 25,
                "soft_limit": 20,
                "type": "connections"
            },
...

```

Though, it behaves as if `hard_limit` was set to `1`.

Besides, I notice that `kill_timeout` and `services.tcp_checks` sections are also different from what’s defined in my Machine app’s [`toml`](https://github.com/serverless-dns/serverless-dns/blob/693f54517/fly.machines.toml) that I `flyctl deploy -c` deployed with.

---

<div class="post-metadata">

**Author:** ![eli](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/eli/32/49867_2.png) [@eli](https://community.fly.io/u/eli)\
**Post date:** [September 19, 2022, 10:49pm UTC](https://community.fly.io/t/flyctl-deploy-does-not-honour-all-entries-in-config-for-machine-apps/7269/2 "2022-09-19T22:49:36Z")

</div>

`fly config` definitely has some rough edges. As you’ve probably noticed, the limits you’re getting in `fly config` getting are the defaults. I’d imagine you might have a better time using the API to create/update machines for now,

The `fly machines` subcommands all are fine to use, but things like `fly config` or `fly secrets set` aren’t the most stable yet. Of course, we are aiming to someday have `flyctl` be fully compatible with machines apps!

---

<div class="post-metadata">

**Author:** ![ignoramous](https://avatars.discourse-cdn.com/v4/letter/i/a9adbd/32.png) [@ignoramous](https://community.fly.io/u/ignoramous)\
**Post date:** [September 20, 2022, 12:19am UTC](https://community.fly.io/t/flyctl-deploy-does-not-honour-all-entries-in-config-for-machine-apps/7269/3 "2022-09-20T00:19:37Z")

</div>

> [@eli](#):
>
> I’d imagine you might have a better time using the API to create/update machines for now,

Yikes, no. I like my `flyctl`. I’ll patiently wait in the bushes for it to mature.

What led me astray was, the preview announcement on the forum mentioned that `flyctl deploy -c` would work like one would expect it to…

> [@eli](#):
>
> Of course, we are aiming to someday have `flyctl` be fully compatible with machines apps!

Any timelines?