jpmorganchase/fusion-java-sdk

A Java SDK for the Fusion platform API

fusion-java-sdk's Issues

Integrate Karate Tests

Multipart download support

test

SDK API Design

Decision to be taken over which parts of the SDK should be exposed with public interfaces versus hidden

Update examples

Add additional examples in README to cover common use cases

Review and supplement logging

Verify Download Digest

Multipart Upload support

Refactor Fusion tests to reduce duplication

Remove 'pact-samples' folder from test/resources

Add Configuration Item to Manage in-flux Data

Review package usage from core Java SDK to ensure correct, modern implementations are being used

Handle SSE Notifications

e2e integration tests

Initial work was started on this (splitting the integration tests out by tag and running under failsafe), but more test cases need to be added

Github Actions automation

1. Snapshots to be published for anything merged to develop
2. Install build for merges to main
3. Manual action created to publish releases (can only run on release/ branches)
4. Add dependency scanning (Depend-a-bot / Lift / Other)
5. Add static security scanning for code

0.0.6 Candidate Release Issues

Ticket to correct issues discovered during release candidate testing.

Tasks

Beta Give feedback

1. Null pointer when using invalid token
2. Update of documentation on how to construct Fusion Object
3. Report back details of 4xx errors from fusion-api i.e. header validation failures

Force usage of HTTPS

Http client implementation allows HTTP URLs to be passed. This should be changed to allow only HTTPS URLs.

Challenge will be mocking for the proxy scenarios in Wiremock (Wiremock wont work correctly as a proxy for HTTPS traffic)

Refactor JdkClient tests for internal consistency

Cleanup Fusion builder interface

Use builder pattern consistently on the various classes and ensure that our test coverage across the builders is sufficient (e.g. we include enough negative test scenarios)