Refactor export VP creation according to changes in the Signer
Before this change the infohub service created VP itself and just used the signer for acquiring a VP proof. With the new Signer endpoint which can create VP from raw JSON data, the complexity in the export decreased, because the infohub must not create a VP itself - VP creation and VP proofs are completely delegated to the Signer service.
Showing
- internal/clients/signer/client.go 16 additions, 15 deletionsinternal/clients/signer/client.go
- internal/clients/signer/client_test.go 62 additions, 80 deletionsinternal/clients/signer/client_test.go
- internal/service/infohub/infohubfakes/fake_credentials.go 0 additions, 176 deletionsinternal/service/infohub/infohubfakes/fake_credentials.go
- internal/service/infohub/infohubfakes/fake_signer.go 60 additions, 50 deletionsinternal/service/infohub/infohubfakes/fake_signer.go
- internal/service/infohub/service.go 15 additions, 24 deletionsinternal/service/infohub/service.go
- internal/service/infohub/service_test.go 9 additions, 79 deletionsinternal/service/infohub/service_test.go
- internal/storage/storage.go 7 additions, 4 deletionsinternal/storage/storage.go
Loading
Please register or sign in to comment