This message was deleted.

Hey Julien, It looks like there's an issue right now that is manifesting itself. https://github.com/pulumi/pulumi/issues/2753 This means it is also happening in the Azure provider. I can suggest that you need to downgrade the version of Pulumi for now - this should fix the issue. If you can, can you add to that issue that the same issue is happening with Azure? We can then unpublish the provider version I'm sorry this has happened to you

Ok, i'm updating the issue, thanks for your quick reply

sorry again for the issue! Subscribe to the issue and you will know when it's updated

@few-processor-86645 I’m opening a PR to fix this now, and we’ll get a new release ASAP - certainly in the next hour.

Ok, thanks, let me know when it's available I'll try it

Hi @few-processor-86645 - for now we have rolled back the Azure package to the previous version. If you update your

package.json

to point at v0.18.2 (or the

latest

tag) and re-run

npm install

, you should not see this reoccur

I confirm that

Great. There will be a release with the new features but without this bug soon.

If you pick up the latest CLI release -

0.17.13

- you should no longer see these proposed replacements.

I confirm that! Thanks guys

thanks for the fast confirmation - sorry again!