Shell functions vs playbooks #362
ResistanceIsUseless
started this conversation in
Ideas
Replies: 1 comment 2 replies
-
@ResistanceIsUseless I love the idea of cleaning up .zshrc and you are correct about playbooks, they arent used and probably need some attention. Another important part that needs clean up are the packer provisioners. Ideally I image chain of image builders https://medium.com/swlh/chaining-machine-image-builds-with-packer-b6fd99e35049 but thats subject. Anything you can do would be much appreciated. LMK how I can help. I've just been a little busy lately so havent been able to dedicate as much time. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I created an issue to clean up the shell functions since .zshrc is getting pretty long. Maybe this is a better place to start the discussion on that because I feel like playbooks aren't really used(unless i missed something recently). I could see implementing more functions and oneliners to playbooks after we come up with guidelines on what should be a function vs a playbook and how playbooks are used.
My suggestion is we create a separate folder for functions (similar to fish) and functions are only use for OS Utility related commands such as starting and stopping a service or a container. Playbooks will be used for a single command or a one-liner with multiple steps so you don't have remember everything.
Beta Was this translation helpful? Give feedback.
All reactions