-
Notifications
You must be signed in to change notification settings - Fork 35
disable transaction and bulk_transactions extensions by default #236
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
Conversation
Co-authored-by: Vincent Sarago <vincent@developmentseed.org>
Q: should we make
|
I think so -- feels weird to have to specify it if you don't plan on supporting writes. |
Something worries me now. If users want to enable the transaction extension using env variables they will have to set what do we think about a new settings called Note: this is what we do in eoapi-devseed https://github.com/developmentseed/eoapi-devseed/blob/36e0618b6573a7ce243fddd742e83deb397806cd/runtimes/eoapi/stac/eoapi/stac/app.py#L80-L95 |
thanks @jonhealy1 |
Haha I was thinking about changing ours to ENABLE_TRANSACTIONS :) |
|
Ok ok ;) |
* use specific ENV ENABLE_TRANSACTIONS_EXTENSIONS for transactions * Update docker-compose.yml Co-authored-by: Henry Rodman <henry.rodman@gmail.com> --------- Co-authored-by: Henry Rodman <henry.rodman@gmail.com>
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
off
but lets users opt-in via ENABLED_EXTENSIONS environment variable.PR Checklist:
pre-commit
hooks pass locallymake test
)make docs
)