feat: add USER_STAC_COLLECTION_ID_REGISTRY for custom collection IDs#95
Open
feat: add USER_STAC_COLLECTION_ID_REGISTRY for custom collection IDs#95
Conversation
11 tasks
jjfrench
reviewed
Apr 14, 2026
| from stac_pydantic.item import Item | ||
|
|
||
|
|
||
| class TestIsAuthorized: |
Member
There was a problem hiding this comment.
Possibly a parameterized test scenario
jjfrench
approved these changes
Apr 14, 2026
Member
jjfrench
left a comment
jjfrench
left a comment
There was a problem hiding this comment.
Changes look good. Is this expected to be a short-term fix for the collection in discussion or are we going to maintain an authorization list?
Collaborator
Author
It is temporary. We will defer collection id management to the JPL side soon. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 is a temporary setup to enable certain MAAP users to publish to certain named STAC collections. To authorize one or more users to publish to a collection or a wildcard prefix we will add an entry to the
USER_STAC_COLLECTION_ID_REGISTRYe.g.{"collection-id": ["user1", "user2"]}. I don't expect this to get used for long but it will unblock the TROPESS use-case while we sort out the architecture for the JPL-managed collection id reservation process.Resolves #91