-
Notifications
You must be signed in to change notification settings - Fork 39
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[MDS-5697] Add method to forward UNTP DCC's through Orgbook Publisher (…
…#3289) * attestation type and use published vocab * need tupe * update dcc construction and library to dcc 0.3.10 * update test * test * remove/update logging * ensure query doesn't include regional mines (yet * make context files configurable. based on UNTPDCC and BCMinesActPermitCredential versions * real context extension * remove type not defined in context files. update context reference to 0.5.0 * add schema file and config, updated to match 0.1.0 of models package * nullable but not defaulted. * same with product * same for ca * link to credential, not orgbook identifer. * real tdw registry, and schema extension * Define verification method, strip did stop using sovrin did, just use did:web from tdw server. * add permit_number, remove name. * extended class needs extended type * name is required in model (But not in spec) remove hardcode from id path * bc prefix is removed * vcdm 2.0 updates. name is included, issuanceDate is now validFrom. * update to use new DataIntegrity Proof DI proofs are going to be required by orgbook, but maybe not others. removed other WIP code with different endpoints * remove dup line from merge * remove dup lines from merge. * key 1 is different, signing key is now key-02-multikey * use mine_no ad factility identifier * remove unused urls * new env var for target url and generate id. * remove slash from env var * optional id's are allowed in package * return tuple in error case * add columns and publish all pending records * keep error response if success isn't there. * better names, going to implement both processes * new command to push to publisher for construction and publishing * trying to sync * prettier instead of eslint in vscode
- Loading branch information
Showing
7 changed files
with
129 additions
and
48 deletions.
There are no files selected for viewing
4 changes: 4 additions & 0 deletions
4
migrations/sql/V2024.11.29.13.31__add_columns_to_vc_orgbook_table.sql
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
ALTER TABLE permit_amendment_orgbook_publish_status | ||
ADD COLUMN IF NOT EXISTS permit_number VARCHAR(50), | ||
ADD COLUMN IF NOT EXISTS orgbook_entity_id VARCHAR(50), | ||
ADD COLUMN IF NOT EXISTS error_msg VARCHAR; |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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