terraform-provider-iterative
terraform-provider-iterative copied to clipboard
Some refactoring on leo subcommands
Renamed delete to destroy. Renamed read to status. Restructured base options and moved all subcommands into a single package.
moved all subcommands into a single package
Why? thinking
Is there any reason to keep identical single file packages?
Is there any reason to keep identical single file packages?
~“Namespaces are one honking great idea — let's do more of those!”~ Wrong language! 🤭
It probably boils down to a matter of taste[^1] but, to my mind, it looks cleaner once we introduce subcommands or more complex commands (e.g. #291 or #531) which may be split over several files.
See also docker/cli, kubernetes/kubectl or cli/cli for inspiration.
[^1]: Or lack thereof, you're the wise gopher here.