<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">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.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""></div></blockquote><div><br class=""></div><div>With the fanatical fervor of a hundred angry sysadmins, though I lack the competency of one.</div><div><br class=""></div><div><blockquote type="cite" class=""><span class="" style="display: inline !important;">Does anyone have some tips for doing this?</span></blockquote></div><div><br class=""></div><div>It’s really not much different than versioning anything else in git.</div><div><br class=""></div><div>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.</div><div><br class=""></div><div>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.</div><br class=""><blockquote type="cite" class=""><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">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?</span></div></blockquote></div><br class=""><div class="">My preference is to have build scripts attached to a configuration/deployment management system that can:</div><div class=""><br class=""></div><div class="">1) bootstrap a raw VM and associate it with a configuration management server</div><div class="">2) build the basics of the IdP, pulling in a specific edition of a servlet container, java, and the desired IdP distribution</div><div class="">3) check out a specific tag that has what you want from the repo you want</div><div class="">4) deploy & initialize servlet container</div><div class="">5) sanity check new node if desired, then add to pool</div><div class=""><br class=""></div><div class="">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.</div></body></html>