53c31344fa
- When configuring a provider, the engine can now communicate to the provider if it supports marhsalling secrets as rich values, if so, the provider should return any secret values as typed secret objects. - When configuring a provider, the provider can now communicate if it supports accepting secrets as rich values. When true, the engine should marshall secrets as strongly typed values when passing them to the provider - The resource monitor is agumented such that a client can ask if it understands a given feature. We will use this to test support for secrets, so the language SDKs can understand how they should marshall secrets when calling resource monitor RPCs - Register and Read resource gain additional flags to let the resource monitor know if the client can understand secret values being passed back as a the result of a call. |
||
|---|---|---|
| .. | ||
| go | ||
| nodejs | ||
| proto | ||
| python | ||
| README.md | ||