Hi - we sent in an email support question about this but I thought I’d post here as well. We’re trying to make our CI/CD pipeline compatible with your v2 so that we can move to a machines-based app. Currently our workflow does this:
flyctl deploy <some stuff here> --build-arg dev <some more stuff here>
However, it seems that fly machines run does not have that option.
Is there a way to do the same with the new command? I see there’s an --env option. Would this help us?
Thanks.
Hi @enaia
Unfortunately --env will affect the runtime environment not the build environment.
Rather than reworking your pipeline to use the machines command though, you could instead continue to use deploy and use the --force-machines argument.
(--build-arg in fact can be used with machines run, it’s just hidden as it’s not something we expect people to need all that often.)
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.