Allow custom s3 endpoints when configuring custom extensions

[timorusky]

Proposal

The current implementation of the extension-installer command does not allow passing a custom endpoint to the AWS S3 sdk. Since there are dozens of hosters that offer s3 object storage (like DigitalOcean), passing a custom endpoint would allow people bound to other providers to install custom extensions.

Use-Case

No response

Is this a feature you are interested in implementing yourself?

Maybe

Anything else?

No response

[timorusky]

I have proposed a solution in #672, would love to discuss it!

[spron-in]

Thanks @timorusky ! Appreciate it :)

Folks will storm through it and review. BTW, as a product person I would be curious to learn about your use case for custom extension. How do you use it? What worked, what did not?

If don't want to type - we can jump into zoom. Just let me know :)

[timorusky]

@spron-in Hi, thanks for reaching back! My use case for custom extensions is really not that exciting. I'm currently evaluating a migration of a rather small Postgres cluster from GoogleSQL to a managed Kubernetes cluster. Since the databases are quite simple in structure, I will be migrating from PostgreSQL 9.6 to 15 and was planning to use the pglogical extension for this to avoid data loss by utilising logical replication.

[spron-in]

@timorusky nice! Thanks for sharing.