Skip to content

Releases: MSUSEL/msusecl-pique-data

2.0.2

08 Sep 20:21

Choose a tag to compare

This release includes support for a new GraphQL query for use with the WebPique model

2.0.1

31 Mar 19:57
4d7d42b

Choose a tag to compare

Minor security patch. No change to functionality

2.0.0 Release

10 Mar 16:51
3fffec8

Choose a tag to compare

v2.0.0 creates a breaking change around how database results are handled.

  • getCve() will now return a java Optional which must be handled by the end user. If no value is returned from the database for a given query, an Optional.empty() object will be returned
  • getCwe() will return an empty arrayList in the event of a no value result to a database query.
  • The DataAccessException will only be used to indicate that there was an error with a connection or query. try-catch blocks will no longer suffice for handling the "no result" scenario.

1.1.0

23 Jan 16:29

Choose a tag to compare

This release marks a more stable era in development for this library. Many of the pain points in the original formulation of this project have been resolved and the user experience is much improved. A few highlights follow.

  • A docker image, updated daily, is now available to users. This vastly simplifies the process of setting up portable nvd mirrors. Instructions are included in the README.
  • Authentication to either the on-prem or dockerized nvd mirrors is now possible through either a configuration file or environment variables.
  • Documentation through the top level README now accurately describes how to configure and use an NVD Mirror and Pique Data's built-in queries.
  • The database context variable is no longer used and the data source is chosen by configuration file/env variables alone.
  • The PiqueDataFactory class simplifies the instantiation of presentation layer classes. Additionally, dependency injection is now used extensively through the project to improve maintainability and extensibility.
  • Checked exceptions have been converted to unchecked exceptions. Though try-catch blocks are still a best practice, they are not required for use with queries to either the NVD or a mirror.