Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chaincode package golang #94

Open
channingduan opened this issue Feb 15, 2023 · 4 comments
Open

chaincode package golang #94

channingduan opened this issue Feb 15, 2023 · 4 comments

Comments

@channingduan
Copy link
Member

No description provided.

@bestbeforetoday
Copy link
Member

bestbeforetoday commented Feb 15, 2023

I don't think we should be spending time implementing support for the legacy (Fabric v1.x) chaincode packaging.

The Fabric v2.x chaincode packaging is a well-defined tar/gzip file structure. Tools and libraries already exist for creating tar/gzip files so I don't see a lot of value in providing explicit support for creating them in the admin SDK either.

@stale
Copy link

stale bot commented Jun 8, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 8, 2023
@davidkhala
Copy link
Member

davidkhala commented Sep 6, 2023

I don't think we should be spending time implementing support for the legacy (Fabric v1.x) chaincode packaging.

The Fabric v2.x chaincode packaging is a well-defined tar/gzip file structure. Tools and libraries already exist for creating tar/gzip files so I don't see a lot of value in providing explicit support for creating them in the admin SDK either.

Maybe we can consider 1 option if we really want to provide something here: A validator (func or binary) that make sure the provided tar/gzip is under well-defined file structure.

@stale stale bot removed the stale label Sep 6, 2023
@bestbeforetoday
Copy link
Member

Would local validation do anything different from the validation that gets done in the peer when installing a chaincode package?

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

No branches or pull requests

3 participants