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.

Sign up for GitHub

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

Jump to bottom

Design for global deployment phases #30

Open

infinisil opened this issue Sep 25, 2020 · 1 comment

Owner

infinisil commented Sep 25, 2020 •

edited

Loading

Continuing from #2 (comment), I'll use this issue to think about how global deployment phases should be declared

Owner Author

infinisil commented Sep 25, 2020

Some features that should be supported:

Phases can produce an output at execution time
The Nix evaluation of phases can depend on the outputs of previous phases
Phases should have some config, which when changed, causes it to be executed again
Phases should be able to persist some state
Phases should be atomic
Phase executions should be rollback-able

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment