-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[sdk/nodejs] Support for calling methods #7377
Conversation
eb6d244
to
6c836ad
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
overall these changes look good. runtime/* has been a been a bug farm and can fail in exciting ways so it would be good to see some tests that specifically exercise the call
failure path if at all possible. We have some runtime register resource tests that do this:
pulumi/sdk/nodejs/tests/runtime/props.spec.ts
Line 361 in e955a6b
describe("resource error handling", () => { |
@@ -101,27 +101,27 @@ export async function streamInvoke( | |||
const req = createInvokeRequest(tok, serialized, provider, opts); | |||
|
|||
// Call `streamInvoke`. | |||
const call = monitor.streamInvoke(req, {}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did this change b/c of a lint issue w. shadowing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
`__provider` is already used by the dynamic provider `Resource` class, so we need to use another property name here.
6c836ad
to
1e300c9
Compare
Support for calling methods from Node.js.
Part of #7072