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
oeuftete opened this issue
Dec 11, 2019
· 1 comment
Labels
ConfirmedSalt engineer has confirmed bug/feature - often including a MCVEFeaturenew functionality including changes to functionality and code refactors, etc.ZDThe issue is related to a Zendesk customer support ticket.
To simplify the maintenance and change reporting of ini file management states, especially when building an ini from a standard starting point, it would be useful to have an all-in-one state, perhaps ini.managed.
That state would get the source file, perform the various options and sections modifications to it as in the standalone ini states, and only if that result differs from target.ini would the state return with changes.
The text was updated successfully, but these errors were encountered:
oeuftete
added
Feature
new functionality including changes to functionality and code refactors, etc.
ZD
The issue is related to a Zendesk customer support ticket.
labels
Dec 11, 2019
The proposed feature would be exactly what I need. The workaround has the drawback that if I remove one of the ini modifications from the state and run again, change is not reflected in the target until the source changes and the target is recreated.
ConfirmedSalt engineer has confirmed bug/feature - often including a MCVEFeaturenew functionality including changes to functionality and code refactors, etc.ZDThe issue is related to a Zendesk customer support ticket.
Description of Issue
(ref. ZD-4366)
To simplify the maintenance and change reporting of ini file management states, especially when building an ini from a standard starting point, it would be useful to have an all-in-one state, perhaps
ini.managed
.Here's how it might look.
That state would get the source file, perform the various options and sections modifications to it as in the standalone ini states, and only if that result differs from
target.ini
would the state return with changes.The current workaround looks a bit like:
The text was updated successfully, but these errors were encountered: