![]() ![]() In turn, the SAAR Team will forward your request to the appropriate system administrator for account creation. Requests that are not digitally/CAC signed will not be processed.ĭISA Personnel (DOD Civilians, Military & Contractors) forward your "Government Supervisor" approved request to for completion of Part III (Security Manager Validation). ![]() **Note** All system access requests must be digitally/Common Access Card (CAC) Signed. Select all appropriate SAAR hyperlinks below, complete blocks 1-16a and 26a-27, digitally (CAC) sign your request and forward to your "Government(DoD)Supervisor" for completion of blocks 17-20b. **Non-DISA Personnel** Your Completed document must accompany your System Authorization Access Request. **Note** DISA Personnel must upload System Rules of Behavior, Acceptable Use Policy Document to the Corporate Management Information System (CMIS). As a standalone consumable library, this package does not need to exist in hyperledger/fabric or be tied to a specific release.NOTE: If you do not have access to the documents linked below, please visit this page and follow the instructions to request a guest account that will be auto-approved for eligible persons.”Ĭlick the following hyperlink read and digitally (CAC) sign: System Rules of Behavior, Acceptable Use Policy. In an effort to make this library as lightweight as possible, we’ve reduced the number of required dependencies to just a handful including the Golang standard library and the following imported hyperledger packages and components:Īs part of this RFC process we would like to also move the configtx package code we’ve already started on in hyperledger/fabric/pkg/configtx to a separate hyperledger/fabric-config repo to remove it from fabric’s release cycle. Example usage tests are also included in the godocs. This package has high coverage of core features on both a unit level and integration test level. Prior artĬonsumable Golang packages have consistent and effective APIs, are well-documented, leverage universal coding standards, and provide useful examples of common usage. Rather than having to manually update bits and pieces of workaround code, consumption of this library will become a consistent method for adopting new features. Rationale and alternativesĮventually it will become too onerous to maintain current workarounds for channel configuration management as new features are added around channel config. Another consideration is this library will only be provided in Golang, but may eventually support TinyGo compilation to WebAssembly for usage as a web module. It could be argued that even if this library exists, no external clients already using configtxgen would want to switch to consuming it. Many potential consumers may already have a stable method for updating configuration transactions and may be unwilling to make amendments to their processes by consuming this library. Reference-level explanationĪPI documentation already exists in the godocs for this package and can be referenced here. Example usage has been included in the godocs for this package and can be referenced for external tooling. Work on this consumable library has already begun in fabric/pkg/configtx and tracked in FAB-17628. Much of the existing process for generating configuration updates is both tedious and error prone involving decoding a config transaction to JSON with the protolator tool and manually modifying fields prior to encoding back to a protobuf and submitting for update. Currently configtxgen is available and frequently misused as a tool for these operations, but it was never intended for production usage. This CLI tool could then pass these parameters down to the configtx package for generating a config update envelope with the computed read and write sets. One example usage case could be a CLI tool for creating config updates that takes as flags properties to be updated alongside an existing config transaction. The motivation for this work is to provide a consistent API that is actually intended for consumption by external clients for any operations involving channel config transactions. This feature will implement a consumable standalone library that supports generating configuration envelopes for operations including application and system channel creation, channel configuration updates, and attaching endorsing signatures to generated envelopes. ![]() ![]()
0 Comments
Leave a Reply. |