Skip to content

21.3.0
Compare
Choose a tag to compare
@weberjm weberjm released this 28 Oct 22:01
· 590 commits to master since this release
v21.3.0
2f796e7
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Features

Development Releases

Webhooks Authorization (#1317)

  • Incoming Webhooks can now be authenticated in one of three ways:
    • HMAC Verification
    • Passing a Bearer Token
    • Using Basic Auth with the credentials of a User in IAM
  • Information about how to implement Authorization can be found in the Webhooks README file

Policy Parsing Framework (#1268)

  • The governance service now has a prototypical framework for automatically parsing policies attached to flow objects, which can be automatically called by the ferryman.
  • This can be used to block the transmission of flow objects if they fail to adhere to certain user-defined conditions
  • Further information can be found in the documentation: OIH Policy Introduction

Data Enrichment Functions (#1277)

  • The data hub now offers a prototypical suite of functions to enrich stored data objects
  • This includes scoring, filtering, formatting, and deduplicating data objects based on user-defined conditions

Enhancements

Move from yarn to npm7 (#1318)

  • We decided to move to npm7 and updated all files accordingly
  • Developers should now use Node 16 + npm> 7 as their environment
  • The lockfile has been rewritten to enable reproducible builds
  • All Docker images have been optimized accordingly and now use Node 16
  • Many libraries have been updated

Service API Responses (#1247)

  • The 404 response is now only used when a resource does not exist to align the system behaviour with REST specifications.

Auth Client Update (#1334)

  • All fields of an Auth Client can be updated

Fixes

Rebound Queues (#1315)

  • Starting with ferryman 2.0.0 rebound queues can be utilized
  • The component orchestrator needs to have at least version 1.4.2 and, if existing, all deployments for components must be recreated (restart)

Get all Secrete for an Auth Client (#1335)

  • Corresponding DAO has been fixed and now allows specific secrets to be obtained

Other

Removal of minikube folder

In order to simplify the maintenance of deployment and development tools, the /minikube folder has been removed. For local installation with minikube, please use the /dev-tools/minikube folder. Future improvements for local installation will be made there.

Assets 2
0 Join discussion