Magic Castle 11.2
This release introduces the ability for Puppet to be event-driven instead of being apply every 30 minutes. The event is handled by Consul which triggers a reload of the puppet agent service. This event is currently triggered by Terraform remote-exec ressource when terraform_data.yaml
or hieradata.yaml
are modified.
Added
- Added a Consul event that can trigger the reload of Puppet agent configuration
- Added the triggering of the consul puppet event when hieradata or terraform_data.yaml
is changed after aterraform apply
. - [puppet] Added the user
sudoer_username
and its authorized_keys to profile::base.
Changed
- SSH public keys can now be added to
public_keys
after the cluster is built,
without rebuilding all instances. - [cloud-init] Changes to cloud-init file are ignored once the instances are created
- [cloud-init] Moved installation of puppet-agent rpm before puppet-server
- [cloud-init] Moved bootstrapping of consul server in
puppet-magic_castle
's bootstrap.sh - [puppet] Bumped puppet-jupyterhub to v3.8.6
- [puppet] Fixed workshop class for guest accounts
Removed
- [puppet] Globus Connect Server V5 class