You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

1.1.4-SNAPSHOT (under development)

WARNING

This is a work in progress. Do not use unless you know what you are doing!

  • Config Binding Service client
    • predefined parsers for input and output streams
      • remove the need for a DCAE application to manually interpret streams_publishes (Sinks) and streams_subscribes (Sources) parts of the configuration
      • available parsers for DMaaP Message Router and DMaaP Data Router streams
      • experimental support for Kafka streams
    • support for other CBS endpoints besides get-configuration: get-by-key, get-all (will introduce minor but breaking changes)
  • DMaaP client
    • ...

Migration guide

All CbsClient methods gets CbsRequest as a first parameter instead of RequestDiagnosticContext. The CbsRequest may be created by calling CbsRequests factory methods. For existing code to work you will need to do the following change:

// From this:
CbsClientFactory.createCbsClient(env)
        .flatMap(cbsClient -> cbsClient.get(diagnosticContext))
        ...

// To this:
final CbsRequest request = CbsRequests.getConfiguration(diagnosticContext);
CbsClientFactory.createCbsClient(env)
        .flatMap(cbsClient -> cbsClient.get(request))
        ...

The similar changes will be required for other CbsClient methods (periodic get and periodic updates).

✔ 1.1.3 (initial release)

  • Config Binding Service client
    • basic functionality
    • CBS service discovery
    • get application configuration as JsonObject
    • periodic query + periodic updates query
  • BCrypt password utility
  • No labels