Match rpc behavior #228
Merged
Match rpc behavior #228
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thomas11
reviewed
Apr 25, 2024
iwahbe
force-pushed
the
iwahbe/match-rpc-behavior
branch
3 times, most recently
from
58eb7eb to
46c2b94
Compare
iwahbe
force-pushed
the
iwahbe/match-rpc-behavior
branch
from
46c2b94 to
6b5feb7
Compare
thomas11
approved these changes
Apr 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While working on pulumi/pulumi-pulumiservice#258, I noticed that native providers receive unknown values over the wire regardless of configure options. This reflects that in the
rpcmiddleware.