accessclinicaldata.niaid.nih.gov/manifest.json

Deployment changes

• awshelper
  • Manifest.json files MUST be changed to use the new "batch-export-sa" service account and the "BUCKET" environment variable must be set to the batch-export-g3auto secret with the "bucket_name" key. You also no longer need to mount the batch-export-g3auto secret as this is now deprecated (it is replaced by the batch-export-g3auto configmap). (IRSA Changes cloud-automation#2531)
  • "serviceAccountName": "batch-export-sa"... (IRSA Changes cloud-automation#2531)
  • name: BUCKET (IRSA Changes cloud-automation#2531)
  • valueFrom: (IRSA Changes cloud-automation#2531)
  • configMapKeyRef: (IRSA Changes cloud-automation#2531)
  • name: batch-export-g3auto (IRSA Changes cloud-automation#2531)
  • key: bucket_name (IRSA Changes cloud-automation#2531)
  • Remove the following: (IRSA Changes cloud-automation#2531)
  • "volumeMounts": [ (https://github.com/IRSA Changes cloud-automation#2531)
  • { (IRSA Changes cloud-automation#2531)
  • "name": "batch-export-creds-volume", (IRSA Changes cloud-automation#2531)
  • "readOnly": true, (IRSA Changes cloud-automation#2531)
  • "mountPath": "/batch-export-creds.json", (IRSA Changes cloud-automation#2531)
  • "subPath": "config.json" (IRSA Changes cloud-automation#2531)
  • } (IRSA Changes cloud-automation#2531)
  • ], (IRSA Changes cloud-automation#2531)
  • }, (IRSA Changes cloud-automation#2531)
  • "volumes": [ (https://github.com/IRSA Changes cloud-automation#2531)
  • { (IRSA Changes cloud-automation#2531)
  • "name": "batch-export-creds-volume", (IRSA Changes cloud-automation#2531)
  • "secret": { (IRSA Changes cloud-automation#2531)
  • "secretName": "batch-export-g3auto" (IRSA Changes cloud-automation#2531)
  • } (IRSA Changes cloud-automation#2531)
  • } (IRSA Changes cloud-automation#2531)
  • ], (IRSA Changes cloud-automation#2531)
  • Need to mount the configuration files in "requestor" and "metadata" directories to accommodate the new Dockerfile for these services. (adding changes for new al image changes cloud-automation#2661)
  • We are also using Poetry to manage virtual environments instead of python, so the command to run alembic needs to be modified. (adding changes for new al image changes cloud-automation#2661)
• fence
  • activation of the feature depends on a new configuration setting: ALLOW_NEW_USER_ON_LOGIN (Feat: only allow login of onboarded users fence#1184)
  • any env that has S3 buckets in fence config that has wildcard characters should consider adopting this release (Fix/bucket name fence#1193)
• guppy
  • To enable this feature in helm charts add "allowRefresh": {{ .Values.allowRefresh }} to gen3-helm/helm/guppy/templates/guppy_config.yaml and then in your values.yaml file, specify allowRefresh as the boolean true value. (Feature/refresh guppy#273)
• portal
  • new config option dataDictionaryVersion that can be set to "new" or something else. If "new", then the new data dictionary component is loaded. This is a temporary solution until we have fully deprecated the old one. (Feat: enable old and new data dictionary for VA data-portal#1613)

Breaking changes

• fence
  • remove role field from /admin/user POST endpoint (Feat: remove role from POST /admin/user endpoint fence#1202)
  • set User.is_admin to DEPRECATED (Feat: remove role from POST /admin/user endpoint fence#1202)
  • deprecation notices for future breaking changes where we'll remove a number of legacy endpoints (Feat: deprecate legacy unused /admin/ endpoints fence#1201)
  • some of the admin endpoints and methods now expect username instead of name. (Feat: add support for soft delete user fence#1189)