refactor: pause deployments when overdrawn #2011
Draft
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.
Description
WIP
Refactors the behavior of deployments and deployment groups when accounts are overdrawn. This is an initial update that will likely go through several iterations (within this PR and/or via multiple PRs).
While the current design is impressively clean, there are multiple use cases flowing through common code related to this refactor, and it's likely the design needs to be further updated with either interface changes and/or strategic use of options to improve readability, enhance overall flow control, and separate the functionality of different use cases.
This change is fairly rudimentary so far, but this establishes some sense of the issue at hand. Nor does this address all of the concerns listed in the issue (yet).
Comments welcome early (as always), but this will be progressing through multiple iterative stages, and may completely change shortly.
TODO
Closes akash-network/support#368
Author Checklist
I have...
!to the type prefix if API or client breaking changeCHANGELOG.md