search

Automattic / vip-cli

The VIP-CLI
https://docs.wpvip.com/vip-cli/
MIT License
58 stars 17 forks source link

`vip dev-env destroy --soft` does not delete the environment #1207

Closed sjinks closed 1 year ago

sjinks commented 1 year ago

Steps to Reproduce the Problem

vip dev-env create < /dev/null
vip dev-env destroy --soft
vip dev-env list

Expected Behavior

vip dev-env list reports no environments

Actual Behavior

$ vip dev-env destroy --soft
Running validation steps...
✓ Check for docker installation 
✓ Check for docker-compose installation 
✓ Check access to docker for current user 
✓ Check DNS resolution 
no container to killWarning: No resource found to remove for project "viplocal".
✓ Environment destroyed.

$ vip dev-env list
Running validation steps...
✓ Check for docker installation 
✓ Check for docker-compose installation 
✓ Check access to docker for current user 
Found 1 environments:

 SLUG              vip-local                                                                           
 LOCATION          /home/volodymyr/.local/share/vip/dev-environment/vip-local                          
 SERVICES          devtools, nginx, php, database, memcached, wordpress, vip-mu-plugins, demo-app-code 
 NGINX URLS        http://vip-local.vipdev.lndo.site/                                                  
                   https://vip-local.vipdev.lndo.site/                                                 
 STATUS            DOWN                                                                                
 LOGIN URL         http://vip-local.vipdev.lndo.site/wp-admin/                                         
 DEFAULT USERNAME  vipgo                                                                               
 DEFAULT PASSWORD  password                                                                            
 DOCUMENTATION     https://docs.wpvip.com/technical-references/vip-local-development-environment/
github-actions[bot] commented 1 year ago

This issue has been marked stale because it has been open for 60 days with no activity. If there is no activity within 7 days, it will be closed.

This is an automation to keep issues manageable and actionable and is not a comment on the quality of this issue nor on the work done so far. Closed issues are still valuable to the project and are available to be searched.