`flyctl secrets import` before first deployment

[ignoramous]

I’ve hit this too.

@gforrest

I could ignore the unhealthy deployment and set the secrets afterward, but then a legitimate deployment failure wouldn’t be distinguishable from a “successful” failure in CI, so things would be harder to debug and check.

Though I never implemented it, back then I thought an internal-only Fly app (in the same org) to vend out secrets to other apps over 6pn should work just as good. As if, that Fly app was the org’s mono-secret-vault.