How to disable the Transaction extension in the pgstac app?

[jtherrmann]

We're currently using the pgstac app provided here, but we'd like to disable the Transaction extension. We're reluctant to do all of the configuration of the app from scratch. Is there a way to simply disable the extension in the app after it's already been created?

[geospatial-jeff]

Hello @jtherrmann the only way of doing this currently is to configure the app from scratch, the library is designed to do this and we encourage users to configure their own instead of relying on the existing applications (they are really just examples).

That being said we could introduce an environment variable to the pgstac backend which optionally enables or disables the transactions extension, allowing the user to set this at deploy time. This seems reasonable to me.

[jtherrmann]

Thanks for the reply @geospatial-jeff. We like the idea of using an environment variable, so I may open a PR to make that change, if that's alright?

[jtherrmann]

@geospatial-jeff Were you suggesting to introduce an environment variable to enable/disable the Transaction extension just for the example app provided here, or were you intending for the environment variable to affect any app that uses the pgstac backend? The former should be easy to implement, but I'm not familiar enough with the codebase to implement the latter.

Just to clarify, we would actually like to prevent the Transaction extension from being added to the list of extensions, not simply to prevent those endpoints from working (because we would like those endpoints not to appear in the Swagger UI at all).

So it should be simple to check the value of the environment variable and add the Transaction extension to the list here depending on its value.

[jtherrmann]

I opened #495 just to demonstrate the approach I was thinking of.