This enhancement adds the capability to configure your application using CSV files. The configuration is structured around the following classes:
AllowedPublicDid:
Used for managing the publish_did file.
Defines the registered_did attribute, which is a required string and serves as the primary key.
AllowedSchema:
Intended for handling schema files.
Includes attributes like author_did, schema_name, and version, all of which are mandatory and cannot be null.
AllowedCredentialDefinition:
Specifically designed for the credential_definition file.
Contains attributes such as issuer_did, author_did, schema_name, version, tag, rev_reg_def, and rev_reg_entry. All of these attributes are required and must have non-null values.
This enhancement enables you to upload CSV files associated with each
of these classes, using either the POST or PUT methods. The choice
between POST and PUT dictates how the uploaded data interacts with the
existing configuration:
POST: This method will replace the current configuration with the data from the uploaded CSV file.
PUT: In contrast, the PUT method appends the data from the CSV file to the existing configuration, preserving the current state.
This feature enhances the flexibility and ease of configuring your application by allowing you to manage your configuration using CSV files effortlessly.
These enhancements are designed to make your application's configuration management more user-friendly and efficient.
The fields of these CSVs follow the format used in the POST /allow/{publish-data,schema,credential-definition} endpoints
For example the description for the POST /allow/schema endpoint is
This pull request resolves #38
This enhancement adds the capability to configure your application using CSV files. The configuration is structured around the following classes:
AllowedPublicDid:
AllowedSchema:
AllowedCredentialDefinition:
This enhancement enables you to upload CSV files associated with each of these classes, using either the POST or PUT methods. The choice between POST and PUT dictates how the uploaded data interacts with the existing configuration:
POST: This method will replace the current configuration with the data from the uploaded CSV file.
PUT: In contrast, the PUT method appends the data from the CSV file to the existing configuration, preserving the current state.
This feature enhances the flexibility and ease of configuring your application by allowing you to manage your configuration using CSV files effortlessly.
These enhancements are designed to make your application's configuration management more user-friendly and efficient.
The fields of these CSVs follow the format used in the
POST /allow/{publish-data,schema,credential-definition}
endpointsFor example the description for the
POST /allow/schema
endpoint isauthor_did
schema_name
version
and the csv equivalent is
NOTE: All string arguments must be quoted
To append this to the endorsers list of allowed schemas the corresponding curl command would be
For the updated descriptions of the allow lists start the endorser service and open http://localhost:5050/endorser/docs in your browser
The
POST /allow/{publish-data,schema,credential-definition}
describe the correspoinding csv file format.