WIP: Allow override install options

[cevich]

(Note: Untested / speculative change)

It's conceivable that people may want to fork and utilize their own copy
of the aviary repository. Depending on the environment where it's
being installed, various paths and other install-time options may need
to be adjusted. Allow for this by accepting non-default values for
key installer options.

Also, disable existing cron entries with indication of what and when.

Signed-off-by: Chris Evich [email protected]

[mathieulongtin]

How about something like this:
./av setup $INVENTORY_GIT_URI

The inventory contains the config file. The aviary.sh doesn't.
Setup does:

1. clone inventory in temp file
2. read the config
3. create $aviary_root directory
4. move the inventory clone over there
5. run apply for the first time

Adding a cronjob for av should be a module. Not a default behavior.

[cevich]

How about something like this

Heh, unfortunately this is way over my head to understand. I've only just stumbled upon this project, and didn't even make it much past the installer yet 😄

This PR is just about pointing the installer toward a fork and/or different versions or location so it's more friendly to use in CI/CD environments that value stability over features.

Eventually I hope to actually install aviary and play with it some more, it really does appear like a nice simple alternative to Ansible...where I normally end up writing many bash scripts anyway lolz.