# Machines OpenAPI spec omissions

**URL:** <https://community.fly.io/t/machines-openapi-spec-omissions/27255>\
**Category:** General\
**Tags:** wishlist, docs, machines, certificates\
**Created:** [February 28, 2026, 5:54pm UTC](https://community.fly.io/t/machines-openapi-spec-omissions/27255 "2026-02-28T17:54:05Z")\
**Posts on this page:** 1\
**Showing post:** 35

<div class="post-metadata">

**Author:** ![mayailurus](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/mayailurus/32/17593_2.png) [@mayailurus](https://community.fly.io/u/mayailurus)\
**Post date:** [October 15, 2026, 5:58am UTC](https://community.fly.io/t/machines-openapi-spec-omissions/27255/35 "2026-10-15T05:58:57Z")

</div>

> [@praneetloke](#):
>
> Also it looks like multi-containers is only available to certain organizations, so I assume it’s a preview feature?

It did start out that way, but it was opened up to everyone in [April 2025](https://community.fly.io/t/using-containers-with-flyctl/24729) (or earlier).

(There are still some rough edges in the multi-container Machines overall, though.)

> [@praneetloke](#):
>
> The strange thing is, according to the docs, staged secrets would be deployed automatically the next time a machine is updated but that didn’t happen for me. I replaced the machine with a different image and yet the status of secrets in the app are showing as staged.

Hm… I do see the new secret right after updating the Machine, actually, without any intervening steps via `flyctl` or in the dashboard…

```plaintext
$ curl <token-etc> "https://$API/v1/apps/uc15po/secrets/tuna" \
   --data '{"value": "FISH"}'
{"name":"tuna","value":"FISH","digest":"6f0bc02042fd2646",
 "version":123798940,"Version":123798940}
$ cat config-neo.json
{
  "config": {
    "image": "debian:trixie",
    "init": {
      "cmd": ["sleep", "inf"]
    },
    "min_secrets_version": 123798940
  }
}
$ curl <token-etc> "https://$API/v1/apps/uc15po/machines/<machine-id>" \
   --data @config-neo.json
$ fly ssh console
# printenv tuna
FISH

```

(Here `min_secrets_version` [matches](https://community.fly.io/t/flyctl-update-for-managing-secrets/25878) the value returned by the first `POST`, and the rest of `config-neo.json` is the same as when that Machine was originally created.)

How were you determining the status of the secrets? (Some methods of doing so may only be reliable for Machines managed by `fly deploy`, etc.)

---

_[View the full topic](https://community.fly.io/t/machines-openapi-spec-omissions/27255)._