We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Connection config usually contains credentials which is not ideal to store in file system (i.e: sling's env.yaml).
env.yaml
It would be awesome if sling could externalize the connection config.
Something like below:
connections: my_db: config_url: <value>
Where config_url value could be:
config_url
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
The text was updated successfully, but these errors were encountered:
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).
SLING_ENV_YAML
Sorry, something went wrong.
No branches or pull requests
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
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
The text was updated successfully, but these errors were encountered: