feat: WIP implement script to update stac storage metadata #67
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces utilities and enhancements for managing and annotating S3 storage tier metadata in STAC items, focusing on OVHcloud storage classes. The main changes include adding a new shared utility module for storage tier operations, updating the STAC registration workflow to use these utilities, and improving documentation and metadata handling for storage tiers.
New storage tier utilities:
storage_tier_utils.pyproviding functions to:Enhancements to STAC registration:
register_v1.pyto use the new utility functions for extracting region and querying storage tier, replacing previous inline logic. [1] [2]alternate.s3with the detected storage tier (using theovh:storage_tierfield), preserving any existing alternate asset metadata.Documentation improvements:
README_update_storage_tier.mddescribing the update process, usage examples, expected outputs, and related scripts for managing storage tier metadata.These changes make storage tier handling more robust, reusable, and transparent for both new and legacy STAC items.
Contributes to implementation of the 2nd phase 2. Storage Tier Transitions of https://github.com/EOPF-Explorer/coordination/issues/182, as discussed in ADR https://github.com/EOPF-Explorer/coordination/pull/179