Delegate manifest deploy to remote builder #3862
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* use token-token branch of fly-go * reuse deploy token for remote deploys --------- Co-authored-by: btoews <[email protected]>
rugwirobaker
force-pushed
the
delegate-deploy
branch
from
e4d91d4
to
52fe8e5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR builds on top of #3769. We generate a manifest locally then launch a machine
with the deployer image(currently docker.io/codebaker/fly-deployer:5cb86e4), once it's ready we use Execute a remote command
to pass the manifest to a go daemon in the machine to pass it the base64 encoded manifest that it decodes before running
fly deploy --from-manifest.I'm still trying to solve 2 issues here:
the operation I described in the paragraph above to automatically run
fly deploy --from-manifeston next boot.