At one point I went to add a new file in e.g.
`data/data/bootstrap/files/usr/local/bin/foo.sh`
and was confused why it wasn't showing up in `git status`.
It was because the `bin` here also matched the `usr/local/bin`.
This changes the logging strategy so that it logs all output to a local
file in addition to logging at the desired level to the console.
Unfortunately, logrus doesn't have a facility for capturing all log
entries (the hooks are only fired for entries which are at or below the
specified level) so this disables the console output and sets up two
hooks: one for the console and one for the local file.
* platform/metal: trigger bootkube/tectonic via path unit
This removes the need for the last ssh command to the bootkubing
master, which was triggering/running the bootkube/tectonic service
manually in a synchronous way.
This allows for the bootkubing process to be carried-on across
reboots and other failures. The new bootkube trigger is based
on the existence of the shell scripts in /opt.
* gitignore: mask directories crated by smoke test
* modules/bootkube,tectonic,metal: unify bootkube,tectonic units
This moves tectonic and bootkube service and path units into their
respective modules.
It also updates the metal platform to reference the above.
* modules/aws: use path activation for tectonic and bootkube service
This introduces path activation for tectonic and bootkube service
which is necessary for future torcx bootstrapping.
* modules/azure: use path activation for tectonic and bootkube
* modules/openstack: use path activation for tectonic and bootkube
* modules/vmware: use path activation for tectonic and bootkube
* installer: open-source the Tectonic installer
* Jenkinsfile: integrate the Tectonic test/build/release suite
* installer: rename repository in imports, docs and scripts
* installer/server/terraform: copy templates from disk (prev. binassets)
Instead of extracting the TerraForm templates from binassets, find
them on disk (next to the installer's executable and upward in the tree
- or in cwd and upward in the tree) and copy them.
This enables us to bundle the TerraForm templates in the release tarball,
and let users customize them before running the GUI (or use them
directly using TerraForm).
* installer: refactor TF vendoring system to expose multiple providers
* installer/server/terraform/plugins: vendor local,template,aws,matchbox
* installer/vendor: add terraform-provider-matchbox and bump aws-sdk-go
* modules/{bootkube,tectonic}: update custom' providers name/inputs
According to the changes that were made for the upstreaming of these
providers.
* Makefile: drop the unused targets for building custom TerraForm bins
* Documentation: update documentation to use the installer for providers
* bootkube: integrate bootkube render as a module
* tectonic: integrate tectonic asset generation as a module
* platform-aws-asg: embed generated assets in ignition and use them
* embed generated assets in ignition and use them
