storing IDP configs in GIT
Craig Pluchinsky
craigp at iup.edu
Wed Mar 23 07:19:06 EDT 2016
We also use git for conf, edit-webapp, flows, jetty-base, messages,
metadata and views. We stage changes in a testing environment and git
pull those in to prod when ready. I created another properties file that
includes sensitive stuff like passwords and datasealer stuff. Then add
that file to .gitignore since we push to a remote repo.
-------------------------------
Craig Pluchinsky
IT Services
Indiana University of Pennsylvania
724-357-3327
On Wed, 23 Mar 2016, Näslund, Victor wrote:
>
> We handle all our IdP configuration, thats non static files, using puppet which itself is stored in our gitlab.
>
> It works really well since we get the best of both worlds.
>
>
> Victor Näslund
>
> Linux and Identity management
>
>
>
> SMHI / Swedish Meteorological and Hydrological Institute
>
> ITi – IT Infrastructure
>
> SE - 601 76 NORRKÖPING
>
> www.smhi.se
>
>
>
> E-post / Email: victor.naslund at smhi.se
>
> Tel vx/ Phone: +46 (0)11 495 80 00
>
> Direct Phone: +46 (0)11 495 82 46
>
>
> On Mar 23, 2016 01:05, "Nate Klingenstein" <ndk at sudonym.me> wrote:
> Yes I store /config, /metadata as well as UI / UX components (views, messages, edit-webapp) in our local GIT
> solution.
>
>
> We also have a section on this in the Shibboleth Installfest series documentation. There are a couple other directories that may be
> of interest in some deployments, but of course, you should limit it by what you actually modify.
>
> https://spaces.internet2.edu/pages/viewpage.action?pageId=49841792#LinuxIdentityProviderIdPv3(Centos7)-11.CredentialandConfigurationManage
> ment
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>
>
>
More information about the users
mailing list