Add support for secret properties
See original GitHub issueIt’s pretty common to want a separate application.properties
to contains passwords and keys that shouldn’t be checked into version control. Currently this can be done with a profile but it would be nice to support something out of the box.
Issue Analytics
- State:
- Created 9 years ago
- Reactions:7
- Comments:20 (16 by maintainers)
Top Results From Across the Web
Spring Boot Secret Properties: How to store secrets in your ...
In this tutorial, you will learn how to use Spring Boot secret properties in your next application. When you define your own configuration ......
Read more >Secrets | Kubernetes
A Secret is an object that contains a small amount of sensitive data such as a password, a token, or a key. Such...
Read more >Safe storage of app secrets in development in ASP.NET Core
In Visual Studio, right-click the project in Solution Explorer, and select Manage User Secrets from the context menu. This gesture adds a ...
Read more >Secret Backends - Spring
Spring Cloud Vault supports both Key-Value secret backends, the versioned (v2) and unversioned ... The application name is determined by the properties:.
Read more >AWS Secret Manager Service as application properties with ...
Secrets can be database credentials, passwords, third-party API keys, and even arbitrary text. You can store and control access to these secrets centrally...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Both Docker Swarm and Kubernetes can provide secrets by mounting them to a specific mounting point. Suppose the exposed secrets are mounted on
/run/secrets
, then thePropertySource
provider should scan the/run/secrets
directory and for each file add a property named after thefilename
with the file content being the property value.For example, if:
and:
Then this new
PropertySource
provider should add a property nameddatabase_password
with123
as its value.We can consider sensible default values for the Mounting Point, say the
/run/secrets
directory. Also, we could allow developers to customize that directory.In one of our projects, We’ve added the support for Swarm/Kubernetes secrets by registering an
EnvironmentPostProcessor
:We are working on that in spring cloud kubernetes that will be part of the Greenwich release train