You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
This discussion was created from the release 21.3.0.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Features
Development Releases
Webhooks Authorization (#1317)
Policy Parsing Framework (#1268)
Data Enrichment Functions (#1277)
Enhancements
Move from yarn to npm7 (#1318)
Service API Responses (#1247)
Auth Client Update (#1334)
Fixes
Rebound Queues (#1315)
ferryman 2.0.0
rebound queues can be utilizedcomponent orchestrator
needs to have at least version1.4.2
and, if existing, all deployments for components must be recreated (restart)Get all Secrete for an Auth Client (#1335)
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.This discussion was created from the release 21.3.0.
Beta Was this translation helpful? Give feedback.
All reactions