Releases: uc-cdis/hatchery
Releases · uc-cdis/hatchery
2.2.0
Release Notes
For: uc-cdis/hatchery
Notes since tag: 2.1.3
Notes to tag/commit: 2.2.0
Generated: 2024-07-18
New Features
- Add
nextflow-global.s3-objects-expiration-days
setting to configure when
to delete objects created in S3 by Nextflow (#112)
Bug Fixes
- Fix a bug when making requests to Arborist to check users' container
authorization (#112)
Improvements
2.1.3
What's Changed
- Add GH Actions workflow for integration tests by @haraprasadj in #104
- PPS-917 PPS-922 PPS-924 PPS-925 feat: go 1.21 and dep update by @mfshao in #106
- Update instanceProfile in memory during first launch by @jawadqur in #107
Full Changelog: 2.1.2...2.1.3
2.1.2
2.1.1
2.1.0
Release Notes
For: uc-cdis/hatchery
Notes since tag: 2.0.4
Notes to tag/commit: 2.1.0
Generated: 2024-03-25
New Features
- Add
nextflow.instance-ami-builder-arn
setting: the ARN of an AWS image
builder pipeline. Can be overridden by the existingnextflow.instance-ami
setting. Thenextflow-global.imagebuilder-reader-role-arn
setting must be
configured as well for this to work; see docs at
https://github.com/uc-cdis/hatchery/blob/master/doc/explanation/nextflow.md#nextflow-globalimagebuilder-reader-role-arn
(#96)
Improvements
2.0.4
Release Notes
For: uc-cdis/hatchery
Notes since tag: 2.0.3
Notes to tag/commit: bc871cd
Generated: 2024-03-20
Bug Fixes
- Allow
/terminate
to complete when dynamodb query returns nil values
(#100)
Improvements
- Manages gen3-licensed notebook users in dynamoDB table (#89)
- Read prismacloud console version from config, but fallback to v32.02. (#97)
Deployment Changes
- No longer utilizes the
distribute-licenses
cloud-automation cron job for gen3-licensed workspaces
(#89)
2.0.3
2.0.2
2.0.1
2.0.0
Release Notes
For: uc-cdis/hatchery
Notes since tag: 1.6.2
Notes to tag/commit: 2.0.0
Generated: 2024-02-05
New Features
- Nextflow: Support for username placeholder in
job-image-whitelist
configuration (#93)
Bug Fixes
- Nextflow: Configure the AMI for both CPU and GPU instances (#92)
Breaking Changes
- The misnamed
nextflow.instance-type
configuration is now
nextflow.compute-environment-type
, used to configure the batch compute
environment type. A newnextflow.instance-type
configuration can be used
to configure the batch jobs instance type. (#90)