Conversation
…ows eoAPI upgrades)
…ster api setup requirements
| logging.getLogger("mangum.http").setLevel(logging.ERROR) | ||
|
|
||
| handler = Mangum(app, lifespan="auto", log_level="error") No newline at end of file | ||
| handler = Mangum(app, lifespan="auto") No newline at end of file |
There was a problem hiding this comment.
@vincentsarago our stac_api began failing with:[ERROR] TypeError: __init__() got an unexpected keyword argument 'log_level' in the log. @leothomas found that the latest mangum only supports a subset of kwargs which seems to be the problem. Removing log_level lets us deploy the app but do you think we need to handle setting the log level elsewhere and/or pin the mangum version?
There was a problem hiding this comment.
👀 thanks for letting me know this. I think you're safe. I'm not even sure why we set it in the past
| " VALUES " | ||
| " ('context', 'auto')" | ||
| " ON CONFLICT ON CONSTRAINT pgstac_settings_pkey DO UPDATE SET value = excluded.value;" | ||
| )) |
There was a problem hiding this comment.
This works to enable context in stac api results (if it is not set the number matched will always be the request limit or less). I am not sure if this is the right way to make this change. I'm also sure there is a performance hit so we may decide not to enable it but I like it for a sanity check.
There was a problem hiding this comment.
Ah. This is not a good way to handle the change--it fails if it is executed before the migration to pgstac 0.4.3 (the pgstac_settings table doesn't exist in earlier versions).
I'll remove it if I don't find a better way to handle changing the setting.
There was a problem hiding this comment.
Moved the execution of this step further down.
3 participants
What
eoAPI updates
This project is an implementation of the eoAPI which has had recent upgrades and features that were not yet implemented in the delta-backend. This PR upgrades the stac and raster APIs to the latest eoAPI.
cql2-jsonfilter languagemisc updates
How tested
Deployed a temporary 'delete me' stack and loaded test collections and items. Verified tiling works in a notebook and executed simple stac json and cql2-json filter searches. Going forward we will maintain separate dev and prod stacks and can implement automated tests rather than deploying and loading a stack to test each change.