2f60a414c7
As part of pulumi/coconut#94 -- adding targeting capabilities -- I've decided to (yet again) reorganize the deployment commands a bit. This makes targets ("husks") more of a first class thing. Namely, you must first initialize a husk before using it: $ coco husk init staging Coconut husk 'staging' initialized; ready for deployments Eventually, this is when you will be given a choice to configure it. Afterwards, you can perform deployments. The first one is like a create, but subsequent ones just figure out the right thing to do and do it: $ ... make some changes ... $ coco husk deploy staging ... standard deployment progress spew ... Finally, should you want to teardown an entire environment: $ coco husk destroy staging ... standard deletion progress spew for all resources ... Coconut husk 'staging' has been destroyed! |
||
|---|---|---|
| .. | ||
| binder.go | ||
| compiler.go | ||
| eval.go | ||
| new.go | ||
| planapply.go | ||