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.

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

How to identify other storage providers? #22

Closed
m-mohr opened this issue Feb 23, 2024 · 4 comments · Fixed by #24
Closed

How to identify other storage providers? #22

m-mohr opened this issue Feb 23, 2024 · 4 comments · Fixed by #24
Labels
enhancement New feature or request

Comments

@m-mohr
Copy link
Contributor

m-mohr commented Feb 23, 2024

Is there a way to identify other storage providers? The extension seems pretty biased right now towards US services, listing none in the EU for example, only one in China. Using OTHER doesn't let you identify the storage provider and the regions and tiers then are pretty disconnected and not very useful.

@m-mohr m-mohr added the enhancement New feature or request label Feb 23, 2024
@MathewNWSH
Copy link

Hello,

I totally identify with this issue through my use case. I am a developer working with data from the Copernicus program, stored on the CREODIAS cloud, which is part of the Copernicus Data Space Ecosystem.
I believe that for such large and open initiatives like CDSE, this deserves to be emphasized in a form other than "OTHER". At this moment, using a value other than those available causes a validation error for the item.

  • The importance of CDSE's availability among the selected options underscores the fact that it is the official storage for Sentinel mission data.

Regarding Cloud Provider Storage Tiers in the case of CDSE, there is only a standard tier, but there is no minimum duration included.

@fmigneault
Copy link

Same issue for our use case. We use platform-specific hosted data. storage:platform: OTHER seems like the appropriate value, but then users do not have a reference of where/what that "OTHER" is located/is.

@m-mohr
Copy link
Contributor Author

m-mohr commented Mar 12, 2024

I just looked at the extension again and the storage:platform default value is OTHER, so the field doesn't need to be provided so the weird "OTHER" is gone.

Currently, the other pre-defined enum values are also not used to enforce specific values for the other fields so having the enum is a bit useless.

I'm wondering whether we should remove the enum and make it free-text. For the providers where we want to validate specific values, we should create specific sub-schemas for individual proviers (or separate extensions that build on top of storage?)

I'll try to come up with a PR.

@m-mohr m-mohr linked a pull request Apr 25, 2024 that will close this issue
@m-mohr
Copy link
Contributor Author

m-mohr commented Apr 25, 2024

Please review the PR for version 2 that is meant to solve this issue: #24 @fmigneault @MathewNWSH

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants