Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix bug making local-only impossible #15

Merged
merged 1 commit into from
Feb 4, 2022
Merged

Conversation

mveytsman
Copy link
Contributor

@mveytsman mveytsman commented Feb 4, 2022

This PR is unrelated to #14 but can be applied on top of it, they address different issues.

The issue is that $* ends up giving us all the arguments a string, so you're comparing "deploy --local-only" with --local-only, and you end up running the command flyctl deploy --local-only --remote-only. This can't deploy because they cancel each-other out :)

==> Verifying app config
--> Verified app config
==> Building image
Error failed to fetch an image or build from source: docker is unavailable to build the deployment image

The way actions invoked the entrypoint, $* gave us the args in a string so we never succeeded unless the only argument to deploy was `--local-only`, instead we ended up with e.g. `flyctl deploy --local-only -some-arg --remote-only`

`--local-only` and `--remote-only` cancel each other out and we're left unable to deploy.

Also fixes an a bug where we repeated the local strategy e.g.  `flyctl deploy --local-only --local-only`
@jsierles
Copy link
Member

jsierles commented Feb 4, 2022

Nice catch!

@jsierles jsierles merged commit d81c6d5 into superfly:master Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants