You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The deprovision --all command does not deprovision all resources in AWS.
To Reproduce
initiate a copy or sync from any cloud provider to AWS; this provisions a VPC and ancillary resources in AWS
deprovision everything:
skyplane deprovision --all
Expected behavior
All resources created by skyplane in AWS - that is, EC2 instances, instance profiles, security groups, route table associations, VPC endpoints, nacls, subnets, internet gateways, VPCs - should be deleted.
Actual behavior
Only EC2 instance profiles are deleted. EC2 instances themselves are typically already terminated at the end of a copy/sync.
Output:
root@28e526f36e9b:/workdir# skyplane deprovision --allNo instances to deprovision✓ Removing IPs from VPCs (1/1) in 1.95sDeleting firewall rule: allow-default-4db23ad1Deleting firewall rule: allow-default-9bb0b9dfDeleting firewall rule: skyplane-default-allow-icmpDeleting firewall rule: skyplane-default-allow-internalDeleting firewall rule: skyplane-default-allow-ssh
Environment info:
OS: Debian GNU/Linux 11 (bullseye)
Python version 3.9.2
Skyplane version 0.3.2
Additional context
Why isn't delete_vpc invoked when deprovisioning in AWS?
The text was updated successfully, but these errors were encountered:
Describe the bug
The
deprovision --all
command does not deprovision all resources in AWS.To Reproduce
Expected behavior
All resources created by skyplane in AWS - that is, EC2 instances, instance profiles, security groups, route table associations, VPC endpoints, nacls, subnets, internet gateways, VPCs - should be deleted.
Actual behavior
Only EC2 instance profiles are deleted. EC2 instances themselves are typically already terminated at the end of a copy/sync.
Output:
Environment info:
Additional context
Why isn't
delete_vpc
invoked when deprovisioning in AWS?The text was updated successfully, but these errors were encountered: