Closed mdpearson closed 1 year ago
while we're thinking about cleaner ways to do this, I think something like this should be pulled into a separate playbook. Most customers don't use ZeroTier
:+1:
That being said, I'm inclined to keep things as a "monolith" for a little while since it's still under heavy development and we're likely to find more opportunities to split things apart.
I completely agree re: the "monolith" approach. I just wanted to start the conversation about making this more portable since I suspect we might to start opening this up to the community at some point. In fact, I was trying to figure out how to make the ansible playbooks work for a digitalocean instance I created but it was going to be a lot of copy-pasta / contaminating our playbooks for a non-PIH use case.
For example, I could imagine optional playbooks for: zerotier support bamboo support adding users from a JSON file
Yes, I like that. Each one of those could have multiple implementations and/or "databases" (VPN: zerotier, forticlient; CI/CD: jenkins, bamboo, gha; users: PIH, SBHF, etc)
@jmiranda while we're thinking about cleaner ways to do this, I think something like this should be pulled into a separate playbook. Most customers don't use ZeroTier
That being said, I'm inclined to keep things as a "monolith" for a little while since it's still under heavy development and we're likely to find more opportunities to split things apart.
For example, I could imagine optional playbooks for: