Fly’s more strict with secrets (a good thing!), but if folks could set secrets for remote builders, then that should work-out nicely afa devex is concerned?
That is, imagine if fly secrets set k1=v1 k2=v2 -a <free-builder-name> set approp env vars for remote deploys?
fly env set k1=v1 k2=v2 -a <free-builder-name> would also be neat.