Skip to content

Expose a network configuration snapshot to Fabric workloads - #1745

Open
Hanabi9248 wants to merge 1 commit into
hyperledger-caliper:mainfrom
Hanabi9248:codex/fabric-network-context
Open

Hanabi9248 wants to merge 1 commit into
hyperledger-caliper:mainfrom
Hanabi9248:codex/fabric-network-context

Conversation

@Hanabi9248

Copy link
Copy Markdown

Issue/User story

Fixes #1694.

Design of the fix

Add sutContext.networkConfiguration to both Fabric gateway adapters. It contains a deep copy of the parsed configuration so workloads can choose configured MSPs, identities and channels without changing the connector's configuration. Internal connection-profile caches are excluded; referenced files and wallet contents are not expanded.

Validation and automated tests

Both new gateway-context tests fail on main because the configuration is unavailable. They check MSP/channel values and nested mutation isolation; the v2 test also checks that a previously loaded connection profile stays out of the snapshot.

All 243 Fabric unit tests pass, along with changed-file ESLint and the license check. No live Fabric network integration test was run.

Documentation

Updated the Fabric workload initialization documentation with a usage example and the snapshot's scope.

Signed-off-by: Hanabi <317387557+Hanabi9248@users.noreply.github.com>
@Hanabi9248
Hanabi9248 requested a review from a team as a code owner September 15, 2026 21:23

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow a workload access to the parsed support of the network configuration so that it can query information

1 participant