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
DSCv3 currently already emits how long a configuration takes to run, it would be interesting to allow configuration authors to supply this in the metadata section like expectedRuntime to give an idea if it takes minutes, hours, days, etc... which would be presented as progress.
Also allow the same metadata per resource execution.
Perhaps DSC can store how long configurations have taken to run on a particularly system and adjust the estimate for that system. So a high powered system that is fast, instead of taking 2 hours, it take 1.5 hours, so future estimates can be reduced by 25%.
Summary of the new feature / enhancement
DSCv3 currently already emits how long a configuration takes to run, it would be interesting to allow configuration authors to supply this in the metadata section like
expectedRuntime
to give an idea if it takes minutes, hours, days, etc... which would be presented as progress.Also allow the same metadata per resource execution.
Proposed technical implementation details (optional)
No response
The text was updated successfully, but these errors were encountered: