Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Automatically make versioned distribution files read only #3400

Closed
1 of 2 tasks
Tracked by #3375
bendnorman opened this issue Feb 14, 2024 · 1 comment · Fixed by #3421
Closed
1 of 2 tasks
Tracked by #3375

Automatically make versioned distribution files read only #3400

bendnorman opened this issue Feb 14, 2024 · 1 comment · Fixed by #3421
Assignees
@zaneselvans
Labels
cloud Stuff that has to do with adapting PUDL to work in cloud computing context. nightly-builds Anything having to do with nightly builds or continuous deployment. release Tasks directly related to data and software releases.

Comments

@bendnorman
Copy link
Member

bendnorman commented Feb 14, 2024 •
edited by zaneselvans

We should make our versioned distributions (v2024.02.05, v2024.XX.XX...) read-only so we don't accidentally overwrite or delete them. stable and nightly don't need to be read-only because they are expected to change on successfully releases and nightly builds.

Tasks
Beta Give feedback
@bendnorman bendnorman added release Tasks directly related to data and software releases. nightly-builds Anything having to do with nightly builds or continuous deployment. labels Feb 14, 2024
@bendnorman bendnorman mentioned this issue Feb 14, 2024
Merged
@zaneselvans zaneselvans mentioned this issue Feb 14, 2024
Closed
@zaneselvans zaneselvans added this to the v2024.02 milestone Feb 14, 2024
@zaneselvans zaneselvans changed the title Make versioned distribution files read only Automatically make versioned distribution files read only Feb 22, 2024
@zaneselvans
Copy link
Member

zaneselvans commented Feb 22, 2024 •
edited

Hmm, it looks like object level retention policies have to be enabled at the time of bucket creation, and that's not the default.

However we can place a temporary hold on a hierarchy of objects, for example:

gcloud storage objects update "gs://pudl.catalyst.coop/v2023.12.01/*" --temporary-hold

It looks like the analogous feature in AWS is S3 object lock

@zaneselvans zaneselvans self-assigned this Feb 23, 2024
@zaneselvans zaneselvans added the cloud Stuff that has to do with adapting PUDL to work in cloud computing context. label Feb 23, 2024
@zaneselvans zaneselvans linked a pull request Feb 24, 2024 that will close this issue
Address loose ends in versioned release mechanics #3421
Merged
@zaneselvans zaneselvans removed this from the v2024.02 milestone Feb 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zaneselvans zaneselvans

Labels
cloud Stuff that has to do with adapting PUDL to work in cloud computing context. nightly-builds Anything having to do with nightly builds or continuous deployment. release Tasks directly related to data and software releases.
Projects
Catalyst Megaproject
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Address loose ends in versioned release mechanics catalyst-cooperative/pudl
2 participants
@zaneselvans @bendnorman