disable transaction and bulk_transactions extensions by default #236
Conversation
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
Co-authored-by: Vincent Sarago <vincent@developmentseed.org>
gadomski
reviewed
Apr 30, 2025
gadomski
approved these changes
May 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
resolves #231
Related Issue(s):
Description:
It seems hazardous to enable the transactions extensions out-of-the-box because users might not realize that they are enabling users to POST data to the pgstac database. This changes those extensions default to
offbut lets users opt-in via ENABLED_EXTENSIONS environment variable.PR Checklist:
pre-commithooks pass locallymake test)make docs)