Closed trscavo closed 9 years ago
I believe this will be OK, as the current configuration adds this element only if it is not already present. I will verify that this is the case, however, between the 4th and 11th.
Confirmed that the existing configuration for mdq-beta
works with the current InCommon preview aggregate today. I therefore believe that the mdq-beta
deployment will cope just fine when the production aggregate transitions, but of course we will want to verify that after the change goes live.
The InCommon production aggregate transitioned on 2015-02-12; current plan for the fallback aggregate is to transition on 2015-02-19. I'll remove the redundant stage some time after that and before the next deployment cycle.
Transition has occurred with no problems, removing the redundant code is issue #16.
This is just a heads up!
InCommon Operations will add explicit
<mdrpi:RegistrationInfo>
elements to production metadata according to the following schedule:I assume the mdq-server instance at mdq-beta.incommon.org is consuming the main (production) aggregate, in which case the middle date above is most relevant.