This message was deleted.
# general
s
This message was deleted.
e
I think the engine tries to use the old provider for deletes of old resources, worth raising an issue about that version number warning though that seems wrong.
m
I think the engine tries to use the old provider for deletes of old resources
Well, with the outdated plugin, I can easily run a
up
or
preview
, I just get the warning. The provider on the resource is correct. So either the warning being shown is a bug in itself, or it's actually using the old provider but setting the new on the resources.
e
Yeh please raise an issue about this, I can look into it next week. It probably is that the warning is bugged.
m
I've created the issue here: https://github.com/pulumi/pulumi/issues/11916
It probably is that the warning is bugged
I'm leaning more to something trying to use the old provider version, as I get the error when removing the plugin. Unless the warning actually tries reading some information from the provider package for the warning to be rendered.
e
I'm on support rotation next week, promise I'll look into this first thing Monday unless the support engineer beats me to it tomorrow (I'm out of office tomorrow otherwise I'd look into this now)
👍 1
m
An observation, I've also added to the issue, if that's relevant.
Copy code
An observation, that might be a clue, our setup is a mono-repository where we have multiple stacks. All got the provider updated, but only some of the stack are printing the warning. The common denominator between the stacks that print the warning are, they all use custom resource components.