Open Integration Hub
Update for Tenant Ownership of components (#1472)
Fix for kubernetes permission errors (#1475 , #1477)
Other minor bugfixes and docs improvements were also included. For a full changelog, see here
flowExecId
, so that persistent Snapshots will not be deletedIn order to make use of these fixes, Components need to be re-built using the new Ferryman version, 3.0.0.
Added flowExecId, flowId, stepId, userId, tenant, and component function to component log messages for traceability. (#1419 )
Other minor bugfixes and docs improvements were also included. For a full changelog, see here
component.json
and get the callParams
object which is now resides thererequestContentType
strings which are necessary for every swagger client callcomponent.json
helpers.js
filegenerate.js
file to match the functionality we wanted for the abovehelpers.js
customPermissions
by adding the customPermissions
parameter to the createToken method
readRaw permission
does not have to be assigned to the user that starts the flow anymorecredentials_id
to Flow Repository API Docs to match current implementationcredentials_id
can be used to reference secrets in a flowonUpdateSnapshot()
attempted to access this.snapshotRoutingKey
which caused an errorthis.snapshotRoutingKey
, from the call to self.amqpConnection.sendSnapshot()
in Ferryman's onUpdateSnapshot()
functionferryman 2.0.0
rebound queues can be utilizedcomponent orchestrator
needs to have at least version 1.4.2
and, if existing, all deployments for components must be recreated (restart)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.
yarn audit
severity by updating multiple packages (https://github.com/openintegrationhub/openintegrationhub/pull/1282)The Secret Service now supports fetching authorisation tokens from external services that use Session Authorization types. This results in less need for showing passwords in plaintext. (#1242, #1243)
Added basic support for Apple Silicon devices on Minikube (without source code deploy) (#1238)
Provide persistent volumes for InfluxDB and Grafana on Google Cloud (#1240)
Various Dependency Updates
:star: See below for information on using release images in deployment |
---|
We made multiple changes to enable linking of IDs across connected system to ensure that data records can be updated. Read more.
Added basic support for replicating the Component Orchestrator inside of the Kubernetes cluster. This included adding a new "preparing" state for Flows while initializing. Future releases will focus on improving the performance and scalability of replicated Orchestrators.
safeguard.lastLogin
will be updated, but updatedAt
will not be modifed)Our documentation page has been restructured to make it easier to find information. We also worked on updating the content and will invest more time on documentation in the future. Please give us feedback and contribute if you find errors or have requests for more documentation on specific topics.
Upon release, the appropriate Docker Hub versions of all Framework Services will be tagged with the release version. Deployments can then use the release version to ensure interoperability of service capabilities.
It is no longer necessary to include a separate Transformer Component inside of Flows for standard transformations. The Ferryman library now includes a transform()
function to perform this functionality directly inside of a Connector (example).
A new service has been added to the framework called Template Repository. This service contains "recipes" or templates from which Flows can be generated. This allows for the sharing of Flows without leakage of Secrets.
Caching has been added to the Component Orchestrator to help it process flows more quickly.
Deployment scripts for the Reference Implementation on Kubernetes have been updated. Configuration and Secrets have been pulled out of the Deployment files and moved to their own Config Maps and Kubernetes Secret files. This allows users to more easily implement their own deployments based on the Reference Implementation.
In the case of failures when changing Flow states, especially when starting a Flow, inconsistencies could arise between the reported state in the Flow Repository and the Component Orchestrator. Failing Flows will now report their status and be transitioned back to Inactive. This also provides fixes for Flows which were "stuck" in a transitional state.
We want to make it easier for the community to contribute and know where help is needed. As a first step, we will start labeling issues with help wanted.
dev-tools/
The Logging Service was removed from the core framework repository and moved into its own repository. This Service is tightly couple to execution on Google Cloud Platform and aggregated logs from its Cloud Logging service. The Framework is intended to remain agnostic from deployment platform, therefore this service was removed from the monorepo.
Ferryman: v1.1.5 Component Orchestrator: v1.1.5 Attachment Storage Service: v0.0.4 Event Bus: v1.2.0 Secret Service: v1.7.1 Webhooks: v1.2.0 Scheduler: v1.2.0 IAM Utils: v1.6.0