Gen3 Monthly Release 2023.04 qa-heal.planx-pla.net 1680794914

[PlanXCyborg]

Applying version 2023.04 to qa-heal.planx-pla.net

[PlanXCyborg]

qa-heal.planx-pla.net/manifest.json

Deployment changes

• fence
  • Requires a Fence DB migration (PXP-10541 Client credentials rotation fence#1068)
• peregrine
  • The pidgin service can be removed if data-portal is on version 5.4.2/2023.05 or newer. Its functionalities are available at peregrine's /coremetadata endpoint (PXP-10708 Add coremetadata endpoint peregrine#198)
  • ASK AN ADMINISTRATOR TO DELETE THE PIDGIN DEPLOYMENT if you remove pidgin. This is NOT automatic (PXP-10708 Add coremetadata endpoint peregrine#198)
  • Peregrine does not rely on configuration files in the cloud-automation repository anymore. The Peregrine configuration files are in the Peregrine repository. (PXP-10163 Python 3.9 peregrine#191)
• pidgin
  • If you are seeing this message, you are deploying the Pidgin service after it has been deprecated. If you are using Peregrine version 3.2.0/2023.04 or newer AND data-portal version 5.4.2/2023.05 or newer, the Pidgin service can and should be removed. (PXP-10708 Deployment notes for release automation pidgin#48)
• sheepdog
  • Sheepdog does not rely on configuration files in the cloud-automation repository anymore. The Sheepdog configuration files are in the Sheepdog repository. (PXP-6245 PXP-9633 Poetry + Python 3.9 sheepdog#387)

Breaking changes

• indexd
  • Ensure you are using Fence>=2021.10. Remove deprecated GA4GH access endpoints. these have existed (and been used) from the Fence microservice since last year. See cloud automation change here (Revert "Revert "fix(migrate): improve acl->authz migration, remove de… indexd#338)

[PlanXCyborg]

qa-heal.planx-pla.net/manifest.json

Deployment changes

• fence
  • Requires a Fence DB migration (PXP-10541 Client credentials rotation fence#1068)
• peregrine
  • The pidgin service can be removed if data-portal is on version 5.4.2/2023.05 or newer. Its functionalities are available at peregrine's /coremetadata endpoint (PXP-10708 Add coremetadata endpoint peregrine#198)
  • ASK AN ADMINISTRATOR TO DELETE THE PIDGIN DEPLOYMENT if you remove pidgin. This is NOT automatic (PXP-10708 Add coremetadata endpoint peregrine#198)
  • Peregrine does not rely on configuration files in the cloud-automation repository anymore. The Peregrine configuration files are in the Peregrine repository. (PXP-10163 Python 3.9 peregrine#191)
• pidgin
  • If you are seeing this message, you are deploying the Pidgin service after it has been deprecated. If you are using Peregrine version 3.2.0/2023.04 or newer AND data-portal version 5.4.2/2023.05 or newer, the Pidgin service can and should be removed. (PXP-10708 Deployment notes for release automation pidgin#48)
• sheepdog
  • Sheepdog does not rely on configuration files in the cloud-automation repository anymore. The Sheepdog configuration files are in the Sheepdog repository. (PXP-6245 PXP-9633 Poetry + Python 3.9 sheepdog#387)

Breaking changes

• indexd
  • Ensure you are using Fence>=2021.10. Remove deprecated GA4GH access endpoints. these have existed (and been used) from the Fence microservice since last year. See cloud automation change here (Revert "Revert "fix(migrate): improve acl->authz migration, remove de… indexd#338)

[mfshao]

I think we can remove this service now?

[haraprasadj]

we need to change portal version in that case AND data-portal version 5.4.2/2023.05