sparse-intern-71089
01/19/2023, 9:18 AMechoing-dinner-19531
01/19/2023, 11:27 AMmagnificent-scientist-64889
01/19/2023, 11:55 AMI think the engine tries to use the old provider for deletes of old resourcesWell, 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.echoing-dinner-19531
01/19/2023, 12:27 PMmagnificent-scientist-64889
01/19/2023, 12:29 PMIt probably is that the warning is buggedI'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.
echoing-dinner-19531
01/19/2023, 12:30 PMmagnificent-scientist-64889
01/19/2023, 1:33 PMAn 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.