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

do not require export-workspace-enable-merge for StacApiWorkspace #1030

Open
bossie opened this issue Jan 31, 2025 · 0 comments
Open

do not require export-workspace-enable-merge for StacApiWorkspace #1030

bossie opened this issue Jan 31, 2025 · 0 comments
Assignees
@bossie

Comments

@bossie
Copy link
Collaborator

bossie commented Jan 31, 2025 •
edited
Loading

job_option export-workspace-enable-merge was introduced to allow for the merge argument of export_workspace to point to the actual STAC resource instead of treating it like a subdirectory/prefix, without breaking existing clients.

This does not apply to StacApiWorkspace because:

  • it is new so there is no behavior that clients can depend on;
  • its merge argument is a collection ID rather than a path.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bossie bossie

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bossie