feat(titiler-pgstac-api): add titiler-pgstac endpoint

[emileten]

Solves #40 by adding a 'titiler-pgstac' construct, which mirrors the STAC API construct : I essentially

• copy pasted the lib/stac-api folder content into a new lib/titiler-pgstac-api folder
• removed the app.py code and simply wrote from titiler.pgstac.main import app in the handler.py
• adapted the requirements and config.py (titiler.pgstac.main requires the postgres credentials to be set as environment variables)

[emileten]

I tried to deploy, and unfortunately the size of the unzipped package is too large to be used for a lambda function (I think it's because titiler.pgstac has many dependencies), so I have to use a Dockerfile instead, just like it's done here or here (any thoughts @vincentsarago ? Thanks !)

Just pushed the Dockerfile, that works, but need to change the CDK code and test it, so I changed the title of this PR to Draft: *.

[vincentsarago]

@emileten, Dockerimage in Lambda should only be use if absolutely no choice (because it's much slower, at least for dynamic tiling)

I think it's because titiler.pgstac has many dependencies

I've deployed titiler.pgstac in lambda before so I doubt this is the case!

Oh, I misread the comments at first. Yes using simple requirements.txt won't work with CDK. Using custom dockerfile to build the package is the way to go.

as you can see in the dockerfile we do https://github.com/developmentseed/cdk-pgstac/pull/42/files#diff-6b803bce2d18a876f97ed5ee61d6137408b36add96327274f990ff18d81430a4R11-R16 which is cleaning some of the dependencies (already in AWS lambda env). in eoAPI, we also specify --no-binary pydantic (https://github.com/developmentseed/eoAPI/blob/main/infrastructure/aws/dockerfiles/Dockerfile.raster#LL9C88-L9C108) which can also reduce the package size a bit

👍

[emileten]

Great that matches with my understanding ! Thank you!

[emileten]

Any chance someone takes a look in the following days?

@sharkinsspatial ? or anyone else 😄

[vincentsarago]

LGTM but I'm not familiar enough with cdk-pgstac that you might want to wait for @alukach or @sharkinsspatial approval 🤷

[alukach]

Strongly recommended changes:

1. git rm lib/titiler-pgstac-api/runtime/src/.env
2. Don't write the pgstac secret values to stdout.

Otherwise, I think this looks good. Left some other comments but those are mostly focused on upping my understanding on how this work.

[emileten]

@alukach I added most of your suggestions -- good to merge ?

[alukach]

@alukach I added most of your suggestions -- good to merge ?

@emileten I agree with Vincent that injecting secrets as env variables at the CDK level would probably be simpler than doing so in the runtime of the code, but I'm good either way and think you can merge when you feel this is ready.

[alukach]

@emileten Realized I was still marked as "requested changes". I'm good with merging if you are.

[alukach]

@emileten Realized I was still marked as "requested changes". I'm good with merging if you are.

[emileten]

Thanks @alukach ! Should be -- just wanted to check the last comment I haven't read above tomorrow.