Page Comparison

...

• Might not be a good idea, but how about moving idp-conf resources to the project root for IdP V5 ?

  Idea is to support tracking changes of a deployed instance via git.

  For example, workflow would be :

  • checkout idp-conf resources to /opt/shibboleth-idp

  • run installer or copy existing deployment

  • use git to track changes

  If we thought this was worthwhile, probably would need to create a separate repository/project for idp-conf (separate from test, but that might be a good idea anyway, to have an idp-conf-test project).

  The benefit is that during upgrades, it should be possible to look at revision information for config files to know who-changed-what.

  FWIW looks like there is another way to filter idp-conf/src/main/resources and retain history :

  git clone https://git.shibboleth.net/git/java-identity-provider

  cd java-identity-provider

  git filter-repo --subdirectory-filter idp-conf/src/main/resources/

  git remote add source https://git.shibboleth.net/git/java-identity-provider

  git fetch source

Created the following issues as result of discussion regarding how-to-track-configuration-file-changes :

Other