Sprinkles makes it easy to share configuration files between local dev environments without leaking private information. No more passwords in Slack PMs, no more API keys in VCS.
pip install sprinkles-config
Please note that sprinkles has only been tested for Python versions >= 3.6.
Sprinkles reads secrets from AWS secrets manager, and binds them to a template you provide. The templating is based on Jinja2¹, making it flexible enough to work with any text-based configuration format you may be using. Anything from .env files, to Java properties, to yaml.
It has a simple param based CLI API, but can also be executed against a config file to encourage reuse. The config format is TOML-based².
NOTE: Sprinkles will use the AWS profile/credentials configured in the calling shell context, using the standard environment variables³.
- Output config to stdout
third.party.api.endpoint=https://example.com/api/v1
third.party.api.key={{THIRD_PARTY_API_KEY}}
sprinkles --template application.properties.j2 --secret-arn arn:aws:secretsmanager:<region>:<account-id-number>:secret:<secret-name>
- Output to file
sprinkles --template application.properties.j2 --secret-arn arn:aws:secretsmanager:<region>:<account-id-number>:secret:<secret-name> --output application.properties
Sprinkles also makes it possible to have a set of defaults (tracked in VCS).
Add a .sprinklesrc file in your project root. Simply run sprinkles
in the
project root to initialize the config.
.sprinklesrc
[secret]
arn = "arn:aws:secretsmanager:<region>:<account-id-number>:secret:<secret-name>"
[files]
[files.docker-env]
template = "sprinkles-templates/.env.sprinkles"
target = ".env"
[files.application-properties]
template = "sprinkles-templates/application.properties.sprinkles"
target = "src/main/com/example/resources/application-dev.properties"