Destroy about lyra

[scottyw]

Relates to #45

[thallgren]

#45 adds a delete command. The term was chosen because we've used it frequently in our discussions and it's also what D refers to in CRUD. I'm a bit concerned if we want to rename the command to "destroy".

"The infrastructure has been destroyed" sounds to me like it's now completely broken. Smashed to pieces. "The infrastructure has been deleted" on the other hand, sounds like it has been removed and no longer exists.

Is the term "destroy" commonly used by other tools in the domain?

[jdwelch]

I don't feel terribly strongly about it, but I like the connotation with 'destroy' that the action you're taking is serious and irrevocable. 'Delete' is certainly more common, so I'm happy to go with that.

[kenazk]

@thallgren - Is there a version of this where you can destroy all resources that have been created by Lyra vs the provided workflow? Just thinking about the case where someone is iteratively developing their infra by creating one workflow at a time, then borks it, and wants to blow away all resources created.

[thallgren]

@kenazk there are presently two types of deletes that take place. The implicit one that takes place during apply when you remove something from the manifest and the explicit one that you get when you use delete instead of apply on a workflow. There's currently no way to delete everything that lyra has created but it would be easy enough to add a delete --all or something similar.

[kenazk]

Ok. Thanks @thallgren. Let's hold off for now.

Anything else we need to close this feature?