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

Automatic collection generation #52

Merged
merged 2 commits into from
Dec 12, 2023

Conversation

andremacedopv
Copy link
Contributor

  • Create script in the chaincode main package to generate the collections.json file
    • The script is only executed if the -g flag is used
    • The --orgs/-o can be used to pass a list of organizations to be considered when generating the policy
    • The scripts adds the collections according to asset types with readers and the number of orgs being deployed
  • Removed collection files (and added it to gitignore)
  • Added collection generation to startDev and upgradeCC scripts
  • Created a generateCollection.sh script just to generate the collections.json file
    • The script can take multiple -o argumets to determinate the orgs to be considered on the generation
  • Updated the generateTar.sh script to generate the collections.json file
    • The script can take multiple -o argumets to determinate the orgs to be considered on the generation
  • Unrelated to the collections, this PR also features a small fix to the generateTar.sh script so it includes hidden files (such as .env) when compressing the go ccapi

@andremacedopv andremacedopv merged commit e5e0455 into develop Dec 12, 2023
3 checks passed
@andremacedopv andremacedopv deleted the feature/collection-generation branch June 27, 2024 20:01
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.

3 participants