Releases: couchbase/service-broker
Releases · couchbase/service-broker
Version 0.0.11
Update Libraries (#82) Keep things up to date and free of CVEs as best we can.
Version 0.0.10
Break Provisioning into Steps Allows service instances to be broken down into steps, allowing once service to be provisioned, waited for it to start, before provisioning the next. Implements #72
Version 0.0.9
Add List Maps to CRD (#69) This ensures that lists of things have unique entries, or for the most part, unique names and IDs. Not perfect, but an improvement none the less.
Version 0.0.8
Polling Delete Return Type (#64) When this responds with GONE, then it should return an empty object, not an error message. Implements #49
Version 0.0.7
Add External Connectivity Docs (#47) Give the reader some information about exposing the service broker to the wider world in order to facilitate multi-cloud architectures. While we cannot possibly document every cloud ever, at least link to the Kubernetes docs where appropriate and describe any necessary modifications that need to be made. Implements #26.
Version 0.0.6
Refresh REST Mapper Cache (#36) We acknowledge that the discovery API is a very expensive call so cache it for the lifetime of the service broker in order to be a good citizen. However this doesn't handle users adding CRDs after the service broker has been started (or updating and deleting for that matter). By adding a regular cache refresh we are still playing nice but also handling these race conditions. We could do this using CRD events with a watch stream, but that would suddenly require a ClusterRoleBinding which is an unacceptable privilege escalation that would be a barrier to entry. Implements #29 and #30.
Version 0.0.5
More Implicit JSON Serialization (#20) Just taking a string on to the end of a template is very naive, it's entrely possible some clever user will put an action in each if/else clause and we'll miss one. Instead walk the parse tree and augment actions that don't set variables. A more acceptable solution than #19 proposed.
Version 0.0.4
Implicit JSON Serialization (#18) I'm guilty of missing out the json function myself at times, so add it in implicitly. While this works for straight pipelines, it won't for stuff with control flow, so outlaw this for now until we can work out how to do this. It will most likely involve parse trees and augmenting leaves.
Version 0.0.3
Test Singleton Resources (#16) This functionality isn't covered by any existing unit tests, so add in a basic test to ensure it works and is guarded.
Version 0.0.2
Inline Templating (#12) While very safe defining templates in YAML, it was very verbose. I can foresee one of the core complaints to be this, so fix it up. By using a templating based approach we should get control flow (e.g. loops) for free, and more importanlty it's not our problem, the language can be delegated to the go documentation instead. Implements #11.