| ▲ | indigodaddy 6 days ago | ||||||||||||||||||||||
Does the playbook generation have support for some totally custom/one-off application? (Eg, not just system/well-known stuff). If so, that would be insane! | |||||||||||||||||||||||
| ▲ | _mig5 6 days ago | parent [-] | ||||||||||||||||||||||
It does! There are several sort of 'catch-alls' in place: 1) stuff in /etc that doesn't belong to any obvious package, ends up in an 'etc_custom' role 2) stuff in /usr/local ends up in a 'usr_local_custom' role 3) Anything you include with --include will end up in a special 'extra_paths' role. Here's a demo (which is good, helped me spot a small bug, the role is included twice in the playbook :) I'll get that fixed!) https://asciinema.org/a/765385 Thanks for your interest! | |||||||||||||||||||||||
| |||||||||||||||||||||||