This message was deleted.

sparse-intern-71089

02/24/2021, 7:54 PM

This message was deleted.

billowy-army-68599

02/24/2021, 7:56 PM

this is usually because something like an EC2 instance or an ELB with an EIP exists in the VPC

👍 1

billowy-army-68599

02/24/2021, 7:56 PM

check for any stray ELBs is my suggestion

little-cartoon-10569

02/24/2021, 7:57 PM

Sometimes if you delete it via the console, the UI gives more detail on what needs to be deleted. Might not be the case for VPCs, but I've found it helpful for security groups, in the past.

adamant-translator-31969

02/24/2021, 8:10 PM

ok I'll try it... but, if I want to delete the state of this resource (I'll delete vpc from aws console),but I receive

Copy code

pulumi state delete urn:pulumi:develop::mycomponent::awsx:x:ec2:Vpc$aws:ec2/vpc:Vpc::cloud-pulumi --force
 warning: This command will edit your stack's state directly. Confirm? Yes
error: No such resource "urn:pulumi:develop::mycomponent::awsx:x:ec2:Vpcc2/vpc:Vpc::cloud-pulumi" exists in the current state

adamant-translator-31969

02/24/2021, 8:10 PM

😕

billowy-army-68599

02/24/2021, 8:23 PM

you don't need to delete the vpc from your state, what we're saying is that someone has provisioned something in that VPC

adamant-translator-31969

02/24/2021, 8:24 PM

ok i will do what you suggest

2 Views

Open in Slack

Previous Next

Pulumi Community

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.