Config overrides at more granular levels

[huynhe]

Is your feature request related to a problem? Please describe.
Not related to any particular problem.

Describe the solution you'd like
Currently, most of available configuration is managed at the deployment level (e.g. retries, timeouts, etc.). However, as we look more towards a multi-tenant world, enabling more granular configuration would be invaluable and give users more flexibility per tenant.

With that in mind, adding configuration (where applicable) overrides at the tenant and destination level will enable better support for a larger user base.

Describe alternatives you've considered
In theory, we could do multiple deployments of Outpost (per tenant), but this seems to defeat the purpose of the multi-tenancy support that Outpost has.

Happy to discuss other suggestions too!

[alexluong]

Hi @huynhe, thanks for checking out Outpost and sharing your feedback. Can you share more which configuration you'd like to customize per tenant? I understand the motivation but not 100% clear on the use case just yet, would love to learn more if you have examples.