It did start out that way, but it was opened up to everyone in April 2025 (or earlier).
(There are still some rough edges in the multi-container Machines overall, though.)
Hm… I do see the new secret right after updating the Machine, actually, without any intervening steps via flyctl or in the dashboard…
$ 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 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.)