feature: show progress during an actual sync #100
Comments
hbagdi
added a commit
that referenced
this issue
Dec 7, 2019
This commit is less of a feature and more of a refactor. The dry package has been removed and instead the entities and operations are printed to console using the `state.ConsoleString` abstraction. This reduces the maintainence overhead by quite a bit and further reduces the difference between diff and sync mode. This commit is a good example of how the refactoring work on state package done in the 0.6 cycle is paying itself off. Fix #100
hbagdi
added a commit
that referenced
this issue
Dec 7, 2019
This commit is less of a feature and more of a refactor. The dry package has been removed and instead the entities and operations are printed to console using the `state.ConsoleString` abstraction. This reduces the maintainence overhead by quite a bit and further reduces the difference between diff and sync mode. This commit is a good example of how the refactoring work on state package done in the 0.6 cycle is paying itself off. Fix #100
rainest
pushed a commit
that referenced
this issue
Apr 21, 2021
This commit is less of a feature and more of a refactor. The dry package has been removed and instead the entities and operations are printed to console using the `state.ConsoleString` abstraction. This reduces the maintainence overhead by quite a bit and further reduces the difference between diff and sync mode. This commit is a good example of how the refactoring work on state package done in the 0.6 cycle is paying itself off. Breaking Change: Showing progress during sync command could be labeled as a breaking change so we need to document it appropriately in the changelog. Fix #100
AntoineJac
pushed a commit
that referenced
this issue
Jan 23, 2024
This commit is less of a feature and more of a refactor. The dry package has been removed and instead the entities and operations are printed to console using the `state.ConsoleString` abstraction. This reduces the maintainence overhead by quite a bit and further reduces the difference between diff and sync mode. This commit is a good example of how the refactoring work on state package done in the 0.6 cycle is paying itself off. Breaking Change: Showing progress during sync command could be labeled as a breaking change so we need to document it appropriately in the changelog. Fix #100
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of decK v0.6, a
diffcommand shows the changes that will be made.A
synccommand performs those changes but doesn't show what it is doing. With large configurations, having a feedback on how far the sync process has come along can provide a better user experience.The text was updated successfully, but these errors were encountered: