Skip to content

Updates pf8 default url to s3#761

Merged
ahernank merged 5 commits intomasterfrom
pf8-url-update
Apr 23, 2025
Merged

Updates pf8 default url to s3#761
ahernank merged 5 commits intomasterfrom
pf8-url-update

Conversation

@eselimnl
Copy link
Copy Markdown
Collaborator

Hello,
Pf8 data objects are currently stored in both Google Cloud Storage (GCS) and Sanger S3. Based on a recent cost analysis, S3 has been identified as the more cost-effective option. As a result, this PR attempts to update Pf8()'s default URL to point to S3.
Cheers, Eyyub

@eselimnl eselimnl requested a review from ahernank April 15, 2025 13:29
Copy link
Copy Markdown
Collaborator

@ahernank ahernank left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @eselimnl, looks good. If we merge & release here, as the S3 bucket is public, all Pf8 data will be available by default through the API. As you know, this is not currently the case, as the GCS bucket is private at the moment. Can I double check this the expected behaviour that you & @podpearson want now?

@nw20
Copy link
Copy Markdown
Collaborator

nw20 commented Apr 23, 2025

Hi @ahernank - can confirm we are happy to have Pf8 data available now.

@podpearson
Copy link
Copy Markdown
Member

Yes, agreed, happy to have Pf8 data available now. Many thanks @ahernank !

@ahernank ahernank merged commit a74b709 into master Apr 23, 2025
10 checks passed
@ahernank ahernank deleted the pf8-url-update branch April 23, 2025 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants