storing IDP configs in GIT

[Chris Reeves]

On Tue 22 Mar 2016 at 23:52:42 +0000, Andrew Morgan wrote:
> Is anyone storing their IDP configuration in GIT?  I'm looking into ways to
> keep multiple IDP nodes in sync by storing the configuration in GIT. Does
> anyone have some tips for doing this?
> 
> I don't want the IDP to automatically refresh its configuration from GIT,
> but I'd like to be able to trigger an update from GIT.  How can I overlay my
> local mods and config files from a GIT repo?
> 
> I'm sure someone has done this already, so I'm trying to learn from others'
> mistakes!  :)

Hi Andrew,

We store our IdP configuration in a git repo - this isn't a dedicated repo for
Shib config, but is actually the repo for our configuration management system
([puppet]). Our configuration management system will build a server from
scratch, applying our configuration changes to whichever version of the IdP
that we tell it to download. All changes that we make to our IdP are deployed
via puppet, and therefore version-controlled.

We also use [vagrant] in combination with puppet to create and destroy dev
environments at will. With a single trivial command we can build a new, local,
IdP in order to test any significant changes or upgrades before going anywhere
near even our test instance. This has massively increased our agility when
responding to development requests.

I'm more than happy to go into further detail if you need it.

Regards,
    Chris

[puppet] https://puppetlabs.com/
[vagrant] https://www.vagrantup.com/