At my company, for what we deploy as Bash, we take care to write it according to regular software engineering standards (code + tests + doc), build OS-specific packages, distribute them using proper repos (rpm, deb) and bake them into vm machine images/containers where needed. We declare dependencies between packages to specify (versioned) dependencies between different code libraries. Works for us.
Looking at how e.g. some official AWS code is written and distributed in shell (like ec2-instance-connect-config), that's not too far I guess from how even big orgs handle Bash code.
Comments
At my company, for what we deploy as Bash, we take care to write it according to regular software engineering standards (code + tests + doc), build OS-specific packages, distribute them using proper repos (rpm, deb) and bake them into vm machine images/containers where needed. We declare dependencies between packages to specify (versioned) dependencies between different code libraries. Works for us.
Looking at how e.g. some official AWS code is written and distributed in shell (like ec2-instance-connect-config), that's not too far I guess from how even big orgs handle Bash code.
Did this precisely at my previous company doing platform automation. It works but requires upkeep.