finos / backplane Goto Github PK

Enhancement Request

Use Case

Per the DAB topology, it runs on a local desktop and allows DA running locally to connect to it. This should be enforced in Backplane too.

Enhancement Request

Use Case

To streamline version management, ensure consistent versioning and automated release process benefiting development teams and maintaining clear release notes.

semantic-release automates the whole package release workflow including: determining the next version number, generating the release notes, and publishing the package.

This removes the immediate connection between human emotions and version numbers, strictly following the Semantic Versioning specification and communicating the impact of changes to consumers.

Backplane uses semantic release for release automation. The bot account used in automation process is NatWest account.

Workflow Description

Backplane is a project under FINOS. Currently its automated release account is owned by NatWest. Proposal is to replace this account with FINOS account.

Enhancement Request

Use Case

Backplane should conform to DAB connection protocol specifications: https://github.com/finos/FDC3/blob/544-Desktop-Agent-Bridging-Proposal/docs/api-bridging/spec.md#connection-protocol.

Backplane service which exposes web socket connection for its client to connect to, must conform to connection protocol as part of standardization.

Workflow Description

https://github.com/finos/FDC3/blob/544-Desktop-Agent-Bridging-Proposal/docs/api-bridging/spec.md#connection-protocol.

Workflow Examples

... provide one or more concrete examples of the proposed workflow.

Additional Information

Enhancement Request

Use Case

As a developer who wants to use backplane, I want a quick start guide so that I can have a minimal set-up of backplane up and running for integration.

Workflow Description

Navigate to Quick Start section in readme.
There are links to backplane executable to download.
There are links to npm and nuget packages.

🚨 The automated release from the develop branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the develop branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Enhancement Request

Use Case

Connection protocol of backplane with desktop agents must conform to DAB specs, for seamless integration of desktop agents. This requires the backplane to send/receive messages per the defined schema.
https://github.com/finos/FDC3/blob/master/schemas/bridgingAsyncAPI/bridgingAsyncAPI.json

Additional Information

Enhancement Request

Use Case

Backplane JS client should create connection with backplane based on specification https://github.com/finos/FDC3/blob/544-Desktop-Agent-Bridging-Proposal/docs/api-bridging/spec.md#connection-protocol. It should encapsulate and abstract the protocol implementation details for consumers like finsemble.

Workflow Description

JS client expose connect taking parameters needed to pass to backplane as part of connection protocol.
https://github.com/finos/FDC3/blob/544-Desktop-Agent-Bridging-Proposal/docs/api-bridging/spec.md#connection-protocol

Workflow Examples

Additional Information

Enhancement Request

Use Case

.NET client integration test automation with backplane.