Rebase against 0.2.0 #78
Closed
+7,270
−73
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Initial commit for the example contract family. The example contract family is primarily used as a means of documenting the process of writing, building, and extending a contract family. In addition, the example contract family provides a template for building a new contract family. Copying the example contract family to a new directory and editing family.cmake should be sufficient to create a new family. Signed-off-by: Mic Bowman <mic.bowman@intel.com>
Signed-off-by: Mic Bowman <mic.bowman@intel.com>
Adds a simple, getting started target for building and running the example contract. Add a docker target to start a contracts container that is running Jupyter. The current source directory is mounted in /project/pdo/dev inside the container. When used with the Jupyter shell, this provides a relatively easy way to develop and test contracts, specifically the example contract. Do not remove model during docker cleanup. There is no particular reason to remove the downloaded model during docker clean up. This should save some time during build/debug/test cycles. The model can be removed with the clean_model target. Signed-off-by: Mic Bowman <mic.bowman@intel.com>
Adds the basic factory/template model for the example contract. This should allow for, more or less, a cut and paste for creating a new contract that preserved the counter. That is, the factory & template are for the specific contract type and would have to be replaced completely for a new contract. Signed-off-by: Mic Bowman <mic.bowman@intel.com>
Signed-off-by: Mic Bowman <cmickeyb@gmail.com>
Signed-off-by: Mic Bowman <cmickeyb@gmail.com>
Signed-off-by: Mic Bowman <mic.bowman@intel.com>
For consistency of terminology... it is a docker *registry*, not a docker *repository*. Signed-off-by: Mic Bowman <mic.bowman@intel.com>
Update handling of user accounts and permissions to simplify the use of PDO docker images from a registry. Signed-off-by: Mic Bowman <mic.bowman@intel.com>
Signed-off-by: Mic Bowman <cmickeyb@gmail.com> Signed-off-by: Mic Bowman <mic.bowman@intel.com>
Add github workflow to run tests on the default suite of contract families (currently all families). Rather than build the necessary PDO docker images, they are pulled from the github container registry. The tests will fail unless the appropriate images are available. Signed-off-by: Mic Bowman <cmickeyb@gmail.com> Signed-off-by: Mic Bowman <mic.bowman@intel.com>
Update version to 0.2.0 Signed-off-by: Mic Bowman <mic.bowman@intel.com>
This is the initial commit of the identity contract family. All of the basic components are in place: contract build, python and pdo-shell plugins, tests and a minimal amount of documentation. The identity contract itself implements a wallet for managing hiearchical deterministic keys for (by default) ECDSA SECP384-r1. Signed-off-by: Mic Bowman <mic.bowman@intel.com>
…ontract family The signature authority contract extends the basic functions defined in the identity contract to include generation of (signing) verifiable credentials. The VC format used in the signature authority is modified from the W3C definitions to accommodate limitations in the parson-based support for JSON. Specifically, the format uses base64 encoded serializations of the credentials for signature generation and verification. This ensures a consistent format that would be difficult to reproduce with just parson. The format of the credentials is provided in a JSON schema document. Signed-off-by: Mic Bowman <mic.bowman@intel.com>
Signed-off-by: Mic Bowman <cmickeyb@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.