Hi, Luís! Thanks for the SIP.
This is an interesting idea, but I would suggest we go even further and
generalize the idea: we could have an interface for a configuration
manager. This would allow to use local files (`config.py`, like we do
today), remote files, or even store the configuration in a database so
it could be modified without having to restart Superset (we probably
would need to check the code for places that assume the configuration
values are immutable and update them).
Wondering if other people have thoughts on this or what other use cases
we could have.
--Beto
On 2025-12-05 03:34, Luís Duarte wrote:
Hello,
I would like for the dev team to consider the possibility of having the
configuration file on an external source like AWS S3 or AWS Parameter
Store
(and other cloud providers equivalent). The idea would be defining an
environment variable like SUPERSET_CONFIG_URL with in AWS case, the
ARN,
and Superset would fetch it automatically on startup.
The purpose of this is to easily deploy Superset on Cloud Container
services like AWS ECS (and other cloud equivalent services)
Thank you
--
Os melhores cumprimentos,
Best Regards,
*Luís Duarte | Software Engineer*
[email protected]
<https://twitter.com/driverpt> <https://pt.linkedin.com/in/driverpt>
<https://github.com/driverpt>
