2.3.0 - Update Postgres client and Teams notification library

Updates:

• Postgresql client to v16
• MS Teams notification library

2.2.0 - Update Postgres and MongoDB clients

Updates:

• Postgresql client
• MongoDB tooling

2.1.1 - Improve URI parsing for service bindings

Improves URI parsing for service bindings, adds port for well-known schemes if they are missing from the URI. (http -> :80, https -> :443)

2.1.0 - Add SSL configuration for databases

Adds new configuration options for SSL, to allow specifying various SSL parameters for your database connections.
See https://github.com/swisscom/backman/blob/master/docs/configuration.md

• ssl.ca_cert_path: optional, the path to the CA certificate (MySQL, PostgreSQL and MongoDB only)
• ssl.client_cert_path: optional, the path to the client certificate (MySQL and PostgreSQL only)
• ssl.client_key_path: optional, the path to the client key (MySQL and PostgreSQL only)
• ssl.pem_key_password: optional, the password for the PEM Key (MongoDB only)
• ssl.pem_key_path: optional, the path to the PEM Key (MongoDB only)
• ssl.verify_server_cert: optional, whether to verify the server certificate (MySQL and PostgreSQL only)

2.0.2 - Avoid parsing problems with Elasticsearch bindings

Fixes a bug when trying to parse Elasticsearch bindings.

Updates Golang dependencies.

• labstack/echo

2.0.1 - Update labstack/echo and mongodb tools

Updates:

• labstack/echo
• MongoDB tooling

2.0.0 - Service Bindings for Kubernetes, and more..

backman:v2.0.0 experienced some major code refactoring internally and now supports the following new features:

• servicebinding.io spec for Kubernetes deployments
• New, simplified Kubernetes deployment templates and examples
• The ability to configure service bindings and credentials directly in the backman config
• Extensive new documentation
• /healthz endpoint that can be accessed without the need for HTTP Basic Auth (mainly useful for Kubernetes deployments)

Maybe, possibly some breaking changes? (hey, what else are major semver bumps for if not that!? 😂)

• Some reworked API endpoint responses. Check the updated Swagger docs and make sure everything still works fine for you if you are a heavy API user!
• Detection of user-provided services might behave slightly different now due to a refactoring of the entire service config handling code internally. Check if all of your configured services are still working fine if you have been using user-provided services on Cloud Foundry before.

1.32.2 - Update mongodb tools

• Updates MongoDB tooling

1.32.1 - Update dependencies

Updates Golang dependencies.

• labstack/echo
• minio/sio
• x/crypto
• yaml.v3

1.32.0 - Try fallback attempts with different S3 service labels

Adds fallback attempts for trying to autodetect the storage backend with different labels if the S3 service could not be found initially.
One specific such case is the common mistake of forgetting to specify s3.service_label according to what your platform provides.