Details
-
New Feature
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
Description
Instead of (as in Puppet 6.0) resolve all Deferred values at catalog read time it would be much better if Deferred values were resolved as they are needed by resources. The big benefit is that this would enable additional use cases - where it is possible to let changes earlier in the apply cycle affect the values for later resources.
From the perspective of a resource this change would not matter, it simply would not see the Deferred instance (just as when it is deferred up front).