No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

<https://www.pulumi.com/docs/intro/concepts/programming-model/#diff-id-olds-news> states that "olds" is the old output values and "news" is the new input values. Is this a typo? Shouldn't they both be inputs or outputs?

I believe all of the references to this are correct, and there are indeed a couple of the resource provider APIs that do intentionally mix these. 

Are you seeing behavior different from this in any case?

I'm having a hard time debugging what is actually going on. I created an implementation that logs what old/new parameters I get and I'm seeing an unexpected value.

Specifically, check() gets an object containing functions for `newInputs` instead of simple key-value pairs like I was expecting.

Do you have a simple implementation floating around that implements all methods, even the optional ones?

For oldInputs, I see an object containing `__provider` containing source-code as a value (large string).

I think I'm getting the hang of this... slowly :slightly_smiling_face:

there are a couple of simple examples here: <https://github.com/pulumi/pulumi/tree/master/examples/dynamic-provider>

Is there a way to instruct `aws.ec2.Instance` to restart some Javascript variable changes value since the last run? I see the `depends` option but it only lets you depend on full-fledged Resources.