Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Externalize connection config #362

Open
trung opened this issue Aug 21, 2024 · 1 comment
Open

Externalize connection config #362

trung opened this issue Aug 21, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@trung
Copy link

trung commented Aug 21, 2024

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
@trung trung added the enhancement New feature or request label Aug 21, 2024
@flarco
Copy link
Collaborator

flarco commented Aug 21, 2024

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants