Externalize connection config

[trung]

Feature Description

Connection config usually contains credentials which is not ideal to store in file system (i.e: sling's env.yaml).

It would be awesome if sling could externalize the connection config.

Something like below:

env.yaml

connections:
  my_db:
    config_url: <value>

Where config_url value could be:

• aws://secretsmanager?arn=arn:aws:secretsmanager:us-east-1:1111222233334444:secret:mydb&key_prefix=sling
• https://some_config_server/mydb
• file://path/to/config/file

[flarco]

Interesting, thanks for the suggestion.

It's worth mentioning that sling accepts env var SLING_ENV_YAML (just put the whole yaml body in the env var).

[ghost]

@flarco Hi, could I change the env.yaml file directory?

[flarco]

Yes, set SLING_HOME_DIR.

[ghost]

Worked perfectly, thanks, I realized late this was indeed on the docs "environment"

https://docs.slingdata.io/sling-cli/environment