Merge remote-tracking branch 'upstream/main'

README.md

@@ -79,7 +79,7 @@ Once you are done kicking the tires on CF and BOSH, clean up your environment to
 
 1. You must first delete any deployments on BOSH. e.g. `bosh -d cf delete-deployment`
 
-1. `bbl down` with your IaaS user/account information.
+1. `bbl destroy` with your IaaS user/account information.
 
 ### Automating the automation tool
 

deployment-versions.txt

@@ -1,2 +1,2 @@
-- *Current jumpbox-deployment: cloudfoundry/jumpbox-deployment@36c85b41cb4ccd4f18479ccd7101963cf8fd7a1f*
-- *Current bosh-deployment: cloudfoundry/bosh-deployment@ee7d8f8dcb3a35b518bc0c49d22ff8be43431a65*
+- *Current jumpbox-deployment: cloudfoundry/jumpbox-deployment@8eb534f63aea36582082b691659a863be01907d0*
+- *Current bosh-deployment: cloudfoundry/bosh-deployment@eebfbec3e6f9c7dea64c37665f21562693035abf*

docs/cleaning-up.md

@@ -2,10 +2,10 @@
 
 In addition to creating resources for deploying BOSH, bbl has two subcommands
 for assisting you in cleaning up an environment after you are done with it:
-`bbl down` and `bbl cleanup-leftovers`.
+`bbl destroy` and `bbl cleanup-leftovers`.
 
 
-## bbl down
+## bbl destroy
 
 If you have the state file for a working environment, then bbl will destroy
 everything it has created.
@@ -14,16 +14,16 @@ As a safety precaution, bbl will not delete the
 environment if there are running VMs deployed by the BOSH director.
 
 ```
-bbl down
+bbl destroy
 ```
 
 
 ## bbl cleanup-leftovers
 
-Sometimes, `bbl down` isn't enough to do the job.
+Sometimes, `bbl destroy` isn't enough to do the job.
 Perhaps you are in one of these situations:
 
-* `bbl down` failed during deletion and lost information.
+* `bbl destroy` failed during deletion and lost information.
 * The `bbl-state-dir` is on a computer that you no longer have access to.
 * You created resources outside of bbl that you want to nuke.
 * You are running bbl's acceptance tests and they failed, orphaning IaaS resources.
@@ -33,7 +33,7 @@ cli utility [leftovers](https://github.com/genevieve/leftovers) as a
 subcommand in bbl.
 
 You can think of `bbl cleanup-leftovers` as kind of like
-`bbl down --force`, but without the need for a `bbl-state-dir`.
+`bbl destroy --force`, but without the need for a `bbl-state-dir`.
 
 **The filter is very important!**