feat: custom STAC API runtime with collection transactions enabled#97
Merged
Conversation
jjfrench
reviewed
May 19, 2026
jjfrench
approved these changes
May 29, 2026
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 PR adds a custom STAC API runtime for MAAP that we need in order to enable the transactions extension (for /collections routes only). The plan is to enable collection transactions for the DPS (User) STAC first so users on the MAAP Console can "reserve" collections in the DPS STAC by posting them to the DPS STAC API (via MAAP API). The assumption is that collection-wise authentication will be managed on the JPL side.
I set it up to store a basic auth username/password (stored in secrets manager) for now but eventually we will move to a more advanced authentication scheme that will work with the MAAP Keycloak.
Here is a view of the protected endpoints in the swagger ui!
While I was in here I updated some of our unit testing CI and added a local docker network that we can use to test locally.
resolves #98