pulumi/sdk/proto
Matt Ellis 53c31344fa Update RPC Interfaces to Support Secrets
- 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.
2019-05-10 17:07:52 -07:00
..
go Add query mode to the language protocol 2019-05-02 18:08:08 -07:00
analyzer.proto Add license headers 2018-05-22 15:02:47 -07:00
Dockerfile Use nightly protoc gRPC plugin for node (#1948) 2018-09-17 15:16:31 -07:00
engine.proto Update the provider RPC interface (#2512) 2019-03-05 10:49:24 -08:00
errors.proto Allow dynamic-provider to send structured errors 2018-07-02 13:32:23 -07:00
generate.sh Work around commonjs protoc bug (#2403) 2019-01-29 17:07:47 -08:00
grpc_version.txt Add Cancel to gRPC resource provider interface 2018-07-15 11:05:44 -10:00
language.proto Add query mode to the language protocol 2019-05-02 18:08:08 -07:00
plugin.proto Add license headers 2018-05-22 15:02:47 -07:00
provider.proto Update RPC Interfaces to Support Secrets 2019-05-10 17:07:52 -07:00
resource.proto Update RPC Interfaces to Support Secrets 2019-05-10 17:07:52 -07:00
status.proto Allow dynamic-provider to send structured errors 2018-07-02 13:32:23 -07:00