Previously, the library utilized an API from Spring Boot that arrived in
2.1.0. Support for Spring Boot 2.0 compatibility was requested and we can
trivially add that support even though Boot 2.0 is EOL. This change updates
the use of the API to be Boot 2.0 compatible.
Signed-off-by: Ben Hale <bhale@vmware.com>
Previously the code looked for SERVICE_BINDING_ROOT. Given that the
specification states it should be SERVICE_BINDINGS_ROOT, this was wrong. This
change fixes it.
Signed-off-by: Ben Hale <bhale@vmware.com>
This changes makes a bunch documentation improvements, case normalizations,
and general improvements left over from the previous addition of the
Kubernetes Service Binding support.
Signed-off-by: Ben Hale <bhale@vmware.com>
This change updates the name of the artifact so that it's more descriptive and
aligns with other Spring Cloud projects.
Signed-off-by: Ben Hale <bhale@vmware.com>
When key names are potentially ambiguous (does this server-id refer to the vault server?) prefer longer more explicit key names. When there is no ambiguity stick with the existing shorter names.
Signed-off-by: Emily Casey <ecasey@vmware.com>
Autoconfigures spring.security.oauth2.* application properties. The name of the binding will become the name of the client. The name of the provider will be taken from metadata/provider.
Resolves#35
Signed-off-by: Emily Casey <ecasey@pivotal.io>
When a binding is provided as a mounted ConfigMap/Secret pair (containing
metadata and secret values respectively) the files within the metadata and
secret directories will be symlinks to files in a colocated hidden directory
that contains the content. In order to handle bindings presented in this
format a Binding object will ignore hidden files and directories when it is
contructed using a path. This prevents errors that previously occured
when the Binding assumed all metadata and secret entries were regular files, and
attempted to read the content of those directories directly.
Resolves#40
Signed-off-by: Emily Casey <ecasey@pivotal.io>
When a binding is provided as a mounted ConfigMap/Secret pair (containing
metadata and secret values respectively) the files within the metadata and
secret directories will be symlinks to files in a colocated hidden directory
that contains the content. In order to handle bindings presented in this
format a Binding object will ignore hidden files and directories when it is
contructed using a path. This prevents errors that previously occured
when the Binding assumed all metadata and secret entries were regular files, and
attempted to read the content of those directories directly.
Resolves#40
Signed-off-by: Emily Casey <ecasey@pivotal.io>
Adds r2dbc properties for mysql, postgres, sqlserver, oracle, and db2
bindings. This allow bindings to be used with reactive drivers.
Signed-off-by: Emily Casey <ecasey@pivotal.io>
Previously, the implementations of the EnvironmentPostProcessors added
ApplicationEventListener to their interface as well. These implementations
tested fine, but of course since there was no full integration test to ensure
that they were registered I forgot to add them to spring.factories.
This change adds their declarations as ApplicationEventListeners to the
spring.factories file and ensures that the logs are replayed when the
application is finished preparing.
Signed-off-by: Ben Hale <bhale@vmware.com>
