storing IDP configs in GIT

[Nate Klingenstein]

> 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.

With the fanatical fervor of a hundred angry sysadmins, though I lack the competency of one.

> Does anyone have some tips for doing this?


It’s really not much different than versioning anything else in git.

The biggest challenge for me is keeping development configuration separate from production configuration.  You’d like to be able to version each independently and place very strong barriers between production and development keys, config, and other things in version control, but you also generally want to be able to make the rest of the environment identical.

My biggest nightmare is generally someone bringing up a node and associating it with my build management system in an inappopropriate way, so I’m pretty diligent about how nodes are added.

> 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?

My preference is to have build scripts attached to a configuration/deployment management system that can:

1)  bootstrap a raw VM and associate it with a configuration management server
2)  build the basics of the IdP, pulling in a specific edition of a servlet container, java, and the desired IdP distribution
3)  check out a specific tag that has what you want from the repo you want
4)  deploy & initialize servlet container
5)  sanity check new node if desired, then add to pool

I generally treat these VM’s as completely disposable.  You could do the exact same process with Docker as well.  I don’t really have any preference about which.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160322/1df2309e/attachment.html>