You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
StatesCurrent is stored as states_saved.yaml, and StatesDesired is stored as states_desired.yaml.
It is a surprise / hard to discover when one wants to read the previously stored StatesCurrent, and has to remember to use StatesSavedReadCmd instead of StatesCurrent..Cmd.
In
0.0.10
and earlier:StatesCurrent
is stored asstates_saved.yaml
, andStatesDesired
is stored asstates_desired.yaml
.StatesCurrent
, and has to remember to useStatesSavedReadCmd
instead ofStatesCurrent..Cmd
.StatesCurrent
, and needs to pass inStatesSaved
toEnsureCmd
-- they have to map the data type (related:ApplyCmd
should only execute ifStatesPrevious
andStatesCurrent
are in sync #59).To address these:
"desired" should be renamed to "goal".
StatesDesired*Cmd
renamed toStatesGoal*Cmd
states_desired.yaml
renamed tostates_goal.yaml
Name bikeshedding:
Rename
StatesSaved*
toStatesCurrentStored
.Add
StatesGoalStored*
to distinguish betweenStatesGoal
and what was saved.Make sure it is easy to go from
States*Stored
toStates*
.Out of scope:
Rename
DiffCmd
toStatesDiffCmd
(?) -- what about diffing parameters or specs.Store state for each item, even if it was not discovered.
Fixes the ordering in stored files.
StatesDiffCmd
API to make it obvious whether we are diffing:Single profile, single flow:
Multi profile, single flow:
Arbitrary two states.
The text was updated successfully, but these errors were encountered: