[JIRA] (IDP-2108) Work out the Upgrade story

[Scott Cantor (Jira)]

Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on IDP-2108 ( https://shibboleth.atlassian.net/browse/IDP-2108?atlOrigin=eyJpIjoiZTdlZDAwYzY0MGZkNDlkYjg2N2E4MmMwMzE2ZDNjYzMiLCJwIjoiaiJ9 )

Re: Work out the Upgrade story ( https://shibboleth.atlassian.net/browse/IDP-2108?atlOrigin=eyJpIjoiZTdlZDAwYzY0MGZkNDlkYjg2N2E4MmMwMzE2ZDNjYzMiLCJwIjoiaiJ9 )

Just given the fact that we don’t (I think) allow idp.properties to be renamed, I’d probably check for that. We used relying-party.xml because of V2, but we’re past that now obviously.

I think you can proceed on upgrades to just do a standard thing: get the list of enabled modules and re-enable them. The ones that matter that are new shoiuld report themselves as enabled against a V4 tree. It’s just for new installs where we need an explicit list to enable, or…we could even add a setting to the module to expose “enable on initial install”.

Re: system and web.xml, if we’re not actually allowing V3 upgrades, then technically we could just remove the extra logic for system/ (because what’s there should either work or be unused), and I’d get rid of the web.xml scan (for the same reason).

( https://shibboleth.atlassian.net/browse/IDP-2108#add-comment?atlOrigin=eyJpIjoiZTdlZDAwYzY0MGZkNDlkYjg2N2E4MmMwMzE2ZDNjYzMiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-2108#add-comment?atlOrigin=eyJpIjoiZTdlZDAwYzY0MGZkNDlkYjg2N2E4MmMwMzE2ZDNjYzMiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100225- sha1:a5851ae )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20230515/ae70b7bc/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-63a2203b-6cb0-4a67-b7fc-ca68233410cb
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230515/ae70b7bc/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-3c457255-4552-41e2-b946-1e547d5d93eb
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230515/ae70b7bc/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-f31e1891-973a-4ecd-8fb9-413222768db3
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230515/ae70b7bc/attachment-0005.png>