Gen3 Monthly Release 2022.08 qa.planx-pla.net 1661237073

[PlanXCyborg]

Applying version 2022.08 to qa.planx-pla.net

[PlanXCyborg]

qa.planx-pla.net/manifest.json

⚠️ Services on branch

• jenkins
• jenkins-worker
• jenkins-ci-worker
• thor

Deployment changes

• arborist
  • Replace Travis with a GitHub workflow for CI (Fix lint CI + replace travis with GH workflow arborist#150)
• fence
  • Requires a Fence DB migration (Client.redirect_uri is now optional) (PXP-10113 Client credentials grant fence#1033)
  • Requires database migration for a new table to Fence, google Access expiration to add new expires column, and to create iss_sub_pair_to_user table task(qa): Fix analyze data link for jenkins envs #968 Updating QA env with integration202011 qa-brain.planx-pla.net 1602519557 #963 Replace dummy file #973 (Feat/passport fence#964)
  • Requires Arborist >= 2022.04 OR >=3.4.0 (PXP-9480): Support merge param for PUT /resource endpoint arborist#143 (Feat/passport fence#964)
  • To enable Passports -> DRS in an environment you must update Fence Configuration to at a minimum specify GA4GH_PASSPORTS_TO_DRS_ENABLED: true (only do this after coordinating with the environment owner as this has several requirements before it can be enabled, including the need to use Indexd's authz field in ALL records rather than acl) (Feat/passport fence#964)
• portal
  • Added new optional field stridesPortalURL in portal config which can display a link to the STRIDES admin portal on workspace page (HP-708 Feat/multiple paymodels data-portal#978)
  • For decoupled workspace, must work with Hatchery 1.0.0+ (HP-708 Feat/multiple paymodels data-portal#978)
  • See gitops configuration options for tabbed metadata detail vs traditional (Feat/disco tabs data-portal#983)

Breaking changes

• fence
  • URL Signing when no_force_sign query param is provided: Previously Fence would make a decision based off if the data was public and no_force_sign provided. Fence will now NEVER sign if no_force_sign is provided (since the concept of "public" data has been abstracted out of Fence. Data access - public or not - is the sole responsibility of the policy engine). In other words, if no_force_sign is provided at the API level, Fence will respect that regardless of whether the resulting URL will actually work. The default Fence behavior should remain the same. chore/update dd version to 3.6.0 #988 (Feat/passport fence#964)