- Add "enabled" property to JdbcEnvironmentProperties
- Make JdbcEnvironmentRepository configuration depending
on new property
- Add integration test to verify the new property
Fixes gh-1605
Fixes gh-1623
- Add "enabled" property to JdbcEnvironmentProperties
- Make JdbcEnvironmentRepository configuration depending
on new property
- Add integration test to verify the new property
Fixes gh-1605
Fixes gh-1623
The default ssh-keygen command creates unreadable SSH keys for spring-cloud-config. This change provides the exception that people are searching with as well as a resolution to the issue.
Always including application as default so that it can be shared accross all applications to be consistent with other repository implementations.
Sharing secrets to the application from default profile.
Updated the docs to reflect the changes
The description shows what you need to do starting from Vault 0.10.0, now the fresh installation of Vault gives you version 1.3.1. Adding the full property name for those that have nothing to do with vault can come in handy.
Also I think we should change the default to be `kvVersion=2`.
* Documenting changes that resulted from issue 1475
Scott Frederick asked me to document the changes he made while implementing the changes needed for issue 1475 (https://github.com/spring-cloud/spring-cloud-config/issues/1475). This PR adds the details that Scott explained to me. Thanks, Scott. :)
* Accounting for Scott Frederick's feedback
Scott had a clarification in one spot and some more detail in another spot. I made the corresponding changes. Thanks, Scott. :)
