Do we have a good pattern established for something similar to a role cookbook with Habitat? I have to run multiple services on the same VM call it 10-30 different services. What are some good practices? Could you have a “role plan” that brings all 10-30 services together? Should another layer in the stack handle what versions of each Hab package to run and the configuration tomls? Since all services run on the same VM and interface with each other they need to be tested and upgraded together as an overall unit.
This seems like a similar problem as Automate 2 which runs 20 or so different Habitat packages but uses a deployment utility “./chef-automate” to load and configure the Habitat packages. I also noticed the Automate 2 version number looks like the Hab package date stamp so maybe something similar to a “role plan” is being used to tie all the services into an overall unit.