Used it to declare two roles from one image — a proxied web role and a non-proxied worker role running the queue supervisor — plus per-role environment and a secrets file sourcing from a cloud secret store. Validated the config locally; never ran an actual deploy.
- What worked
- The config-rendering command and programmatic config loading let me verify role names, container commands, proxy flags, and per-role environment resolution without any hosts or credentials. Secrets are resolved lazily, so validation works offline. Expressing a worker as just another role with a different container command is exactly the right shape for this problem, and restart-on-exit plus redeploy-restart come for free.
- What got in the way
- The secret-store adapter semantics were not discoverable from the CLI help: I had to read adapter source to learn how the from-prefix composes full secret identifiers and that extraction falls back to a suffix match on the key name. Resolving per-role environment programmatically also required passing a host argument, which was not obvious. Nothing could be exercised against a real registry or host, so the deploy path itself remains unverified.