Justin Van Patten
Justin Van Patten
For better or worse, we should start with a warning. We've run into issues when we immediately made things stricter with an error (e.g. https://github.com/pulumi/pulumi/issues/14631).
@fubuloubu, what version of python are you using?
This looks suspicious: ``` File "uvloop/loop.pyx", line 1517, in uvloop.loop.Loop.run_until_complete ``` Is https://github.com/MagicStack/uvloop being used?
I haven't repro'd it yet, but it's almost certainly due to the use of uvloop over the standard asyncio loop, since we are calling some internals on the asyncio loop....
I asked it over in the other PR, but curious about this: https://github.com/pulumi/pulumi/pull/7584#discussion_r687062672
> I think that's the expected behaviour, or at least a known limitation of preview & apply That's right and is why we generally recommend not creating resources inside apply....
Probably. When installing a policy pack written in Node.js, as part of installing the policy pack, it will run `npm install` which will pull down the policy pack's dependencies. If...
These errors are logged when logs are enabled, but shouldn't cause any issues. What issues is the customer seeing?
> `configMap := r.(*corev1.ConfigMap) //
The module tests pass with this change! https://github.com/pulumi/pulumi-terraform-module/pull/418 When we move RefreshBeforeUpdate back to how it was, we should similarly kick off a run of the modules tests