The previous Connection aggregate in agent_verification is merged into the AuthorizationRequest aggregate.
A new Connection aggregate is added to the agent_identity domain, this also means that two new endpoints are opened:
/connections both GET and POST: For GET additional query parameters can be added, for example: GET 'http://localhost:3033/v0/connections?did=did:example:123'
GET /connections/:connection_id: To query a Connection by connection_id
Note that in this PR the Connection aggregate is not that useful just yet. Once we have figured out a nice ergonomic way for different domains to 'interact' with each other, then connections can be created, or updated based on activity in the verification, issuance or holder domain.
Blocked by
130
Links to any relevant issues
125
How the change has been tested
Added unit tests and added Postman Collection Requests
Definition of Done checklist
Add an x to the boxes that are relevant to your changes.
[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have successfully tested this change in a docker environment
Description of change
There are two important changes in this PR:
Connection
aggregate inagent_verification
is merged into theAuthorizationRequest
aggregate.Connection
aggregate is added to theagent_identity
domain, this also means that two new endpoints are opened:/connections
bothGET
andPOST
: ForGET
additional query parameters can be added, for example:GET 'http://localhost:3033/v0/connections?did=did:example:123'
GET /connections/:connection_id
: To query a Connection byconnection_id
Note that in this PR the Connection aggregate is not that useful just yet. Once we have figured out a nice ergonomic way for different domains to 'interact' with each other, then connections can be created, or updated based on activity in the verification, issuance or holder domain.
Blocked by
130
Links to any relevant issues
125
How the change has been tested
Added unit tests and added Postman Collection Requests
Definition of Done checklist
Add an
x
to the boxes that are relevant to your changes.