Updating Env jcoin.datacommons.io - 2023.01 1674096615

[PlanXCyborg]

Applying version 2023.01 to jcoin.datacommons.io

[PlanXCyborg]

jcoin.datacommons.io/manifest.json

Deployment changes

• metadata
  • configuration files will need to be updated (PXP-8825 & BRH 206  metadata-service#65)
• portal
  • this change assumes WTS is already a core/central service. The dependency is hereby moved to the homepage (instead of the ./workspace page) (Centralize WTS refresh token initialization data-portal#1095)
• sower
• ssjdispatcher

Breaking changes

• arborist
  • The GET /auth/mapping endpoint does not accept username as a query parameter anymore. It only supports parsing the username from the provided JWT. To specify a username, use the POST /auth/mapping endpoint. (PXP-10229 Client auth mapping arborist#153)
• 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)
• metadata
  • The configuration file is not compatible with the previous release. This is due to the new support for defining a schema, new configuration options, and changes to the adapters. (PXP-8825 & BRH 206  metadata-service#65)

[PlanXCyborg]

jcoin.datacommons.io/manifest.json

Deployment changes

• metadata
  • configuration files will need to be updated (PXP-8825 & BRH 206  metadata-service#65)
• portal
  • this change assumes WTS is already a core/central service. The dependency is hereby moved to the homepage (instead of the ./workspace page) (Centralize WTS refresh token initialization data-portal#1095)
• sower
• ssjdispatcher

Breaking changes

• arborist
  • The GET /auth/mapping endpoint does not accept username as a query parameter anymore. It only supports parsing the username from the provided JWT. To specify a username, use the POST /auth/mapping endpoint. (PXP-10229 Client auth mapping arborist#153)
• 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)
• metadata
  • The configuration file is not compatible with the previous release. This is due to the new support for defining a schema, new configuration options, and changes to the adapters. (PXP-8825 & BRH 206  metadata-service#65)

[atharvar28]

Merging this PR as the the commons doesnt use dbgap or google service accounts. Other relevant tests have passed in the CI check
cc : @paulineribeyre