Type: New Feature
Affects Version/s: None
This is a follow-up to
EZ-71. I'm intentionally leaving out implementation details for now, this description will need to be updated after EZ-71 is completed. I just wanted to separate out the R&D work from the actual implementation work, in hopes of making it easier to estimate the tickets.
Basic outline of how to accomplish this seems to be:
- Add a flag to be specified in project.clj, something like :split-bootstraps true, have it default to false for backward compatibility
- update ezbake.rb.mustache and the generate-ezbake-config-file function with this flag
- update default.erb with logic to choose the BOOTSTRAP_CONFIG env variable based on the flag. This seems to be where the absolute path of the bootstrap(s) will be determined (i.e. /etc vs /opt)
- update install.sh.erb with logic to install the services.d directories to the correct paths
The debian/redhat init scripts use the BOOTSTRAP_CONFIG env variable, so it doesn't seem like they will need to be updated.
The exact paths for the two services.d directories in a TK project will have to be decided on/made configurable like :config-dir currently is, which will require changes to tk/core