🚀 Autogenerate Sample Data from Sample Manifests
Is there an existing issue for this?
- [X] I have searched the existing issues
Suggestion
There are a couple problems with Sample Data that we would like to address.
- The sample data being out of date from the SDK
- Storing all the manifest sample data files within this repository
Possible Implementation
The large collection of sample data should be removed in favor of using the code to generate samples.
- [ ] Retain only the sample manifests in the repository
- [ ] Delete other folders all the sample data
- [ ] Create a
generate_sampleworkflow for specifically handling the sample data updates allowing for the Specification to be released WITHOUT the sample data since the code has to update for it to be generated. - [ ] Import the
electionguardpackage from python to generate the sample data on the release workflow - [ ] Ensure the release data is zipped and possibly tarballed (#216 ) and attached to releases
- [ ] Update the Sample Data document. It should mention the same things but refer to the releases and the sample manifests instead of the individual files.
Anything else?
This is currently blocked until electionguard-python 1.4 is released.
This issue replaces #215 to include more detail.
This should handle #219 when complete to ensure this can't repeat itself.
Hi @R-C-Stewart , Keith says that this is blocked until v1.4 is released. I dont see any technical reason for this to be blocked, and Keith did remove the blocked label on Feb 21. Can you confirm that this is unblocked.
@shivbijlani, This can be worked on now. The python CLI has code to do generation of plain text ballots. At the time that this was labeled as blocked the cli did not generate ballots from a manifest yet.