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

Create tool to migrate existing cds/tgz chaincode packages #75

Open
jt-nti opened this issue Nov 25, 2022 · 0 comments
Open

Create tool to migrate existing cds/tgz chaincode packages #75

jt-nti opened this issue Nov 25, 2022 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@jt-nti
Copy link
Member

jt-nti commented Nov 25, 2022

It might help people migrate to the k8s builder if there was a tool to create a template project and seed it with the contents of an existing chaincode package.

Traditional Go, Java, and Node chaincode packages contain the smart contract source code which is compiled by a chaincode builder container. (Note: Java packages may only contain prebuilt jars in some cases.)

Packages for the new lifecycle are just tarballs, and packages for the old lifecycle are protobuf based- see cds-cli for an example of how to read those.

A new repo would be required for the new tool but opening this issue here for discussion.

@jt-nti jt-nti added enhancement New feature or request good first issue Good for newcomers labels Nov 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant