An issue with this approach is that it requires the developer to create a temporary fly.yaml file, pasting in one of the env-specific configs, then, after the launch runs, copy the modified config back into the env-specific config. This is why I suggest providing a -c arg to the launch command from which it will read and to which it will write.
Aside: I'm not sure if feature requests belong here but there didn't seem to be a section for it in the community forum.
On the forum, I explained how I did some scripting of configs for multi-env deploys.
An issue with this approach is that it requires the developer to create a temporary
fly.yamlfile, pasting in one of the env-specific configs, then, after the launch runs, copy the modified config back into the env-specific config. This is why I suggest providing a-carg to the launch command from which it will read and to which it will write.Aside: I'm not sure if feature requests belong here but there didn't seem to be a section for it in the community forum.