Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 10 Next »

1.2.0-SNAPSHOT (ElAlto - under development)

WARNING

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

  • DMaaP client
    • Change the factory so it's more configurable
    • Old DMaaP client is now deprecated

1.1.6 (yet to be released)

Bugfix release:

  • (Old) DMaaP client:
    • Security keys was always loaded from JAR instead of given file system path. Only code using SecurityKeysUtil class had been affected. If you do not use SecurityKeysUtil class or you are using the new DMaaP MR client API (

      org.onap.dcaegen2.services.sdk.rest.services.dmaap.client.{api, model} packages) then you are safe and the update is not required.

1.1.5

  • DMaaP client
    • Force non-chunked transfer encoding, because DMaaP MR does not support chunks.
    • DMaaP MR client API should be used in new code. Some minor incompatible changes can occur but it's more or less done.

1.1.4

  • 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 (introduces minor but breaking changes)
  • DMaaP client
    • New, experimental DMaaP client. It's not ready for use yet (not integration tested with DMaaP instance). However, you can use this API if you target El Alto release (note that some minor interface changes might be introduced).
  • Internals:
    • Improved http client: RxHttpClient
    • RxHttpClient uses chunked transfer-encoding only when content-length is NOT specified.

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