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

move some of plan.go into a proper FSM #3875

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

move some of plan.go into a proper FSM #3875

wants to merge 2 commits into from

Commits on Aug 20, 2024

  1. move some of plan.go into a proper FSM

    this doesn't involve too many code changes, more just shifting code
    around. the reason for doing this is that, if we can move as many partso
    f deploys as possible into an FSM, it lets us more easily resume deploys
    that failed, or from midway through a canceled deploy, or anywhere else
    in a deploy.
    
    I want to make more granular FSM transitions for each individual machine
    too, which I'll either do in a future commit or a future PR. The more
    individual FSM states we can retry, the more granular 'resuming' we can
    do. If we can move other parts of deploys into an FSM, it also gives us
    the ability to resume *those* parts as well. Plus some extra super
    powers like easily cloning apps, more granular view of deploy failures
    in a way that we can retry locally, declaratively configuring a fly app, etc.
    billyb2 committed Aug 20, 2024
    Configuration menu
    Copy the full SHA
    6390a73 View commit details
    Browse the repository at this point in the history

Commits on Aug 26, 2024

  1. amend this commit plz

    billyb2 committed Aug 26, 2024
    Configuration menu
    Copy the full SHA
    60a7198 View commit details
    Browse the repository at this point in the history