3c0376bb8e
This changes two primary things about dynamic providers: 1) Always echo back the __provider upon read, even if there is a missing read function on the dynamic provider. In fact, return the full input state in that case. 2) Store the __provider in the output state of the dynamic resource, in addition to the input state. My recollection of the "model" discussion we had weeks ago was that the output properties are mean to capture the state of a resource in its entirety; not having this meant that refresh would marshal the outputs only, and find on the other side of the RPC boundary that __provider was missing. Note that an alternative to the latter fix would be to use some hybrid of input and output state, as we used to do, by merging property maps. |
||
|---|---|---|
| .. | ||
| nodejs | ||
| proto | ||
| python | ||
| README.md | ||