PowerShell
Support specifying timeout for resources
Summary of the new feature / enhancement
In the Microsoft.DSC section of metadata, allow configuration to specify a timeout. It may also make sense to just have a default timeout so configuration isn't blocked indefinitely.
Proposed technical implementation details (optional)
No response
A few related questions:
- Would it be useful to have a
--timeoutoption on thedsc resource *commands? - Should we consider an API surface for adapters to handle timeouts for their adapted resources?
It probably makes sense to have --timeout for both resource invocation and config invocation at the command-line level in addition to allowing config authors to specify timeouts.
For adapters, I think they should just follow the same contract which is metadata at the resource level should be respected. However, we may need adapters to publish what capabilities they support and perhaps even reject explicitly any metadata it doesn't understand so users don't set something that doesn't apply.