-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add VDR v2 spec, generated code and empty wrapper #2630
Conversation
$ref: '#/components/schemas/DIDDocument' | ||
default: | ||
$ref: '../common/error_response.yaml' | ||
/internal/vdr/v2/did/{did}: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this only resolves did:web DIDs owned by the local node? I think we already have /iam/{did}
which essentially does the same?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have iam/{id}/did.json
which is the public URL where the web DID Document lives.
We do not have a resolve API there. Since v1 might be removed v2 still needs a resolve.
Companion PR: #2631 |
Companion PR can be done in parallel. When implementing the Create on the v2 api, the method specifics on the v1 api can be removed. |
d952474
to
d6a2e0f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
almost, small suggestions
@@ -1,7 +1,7 @@ | |||
version: "3.7" | |||
services: | |||
nodeA-backend: | |||
image: "${IMAGE_NODE_A:-nutsfoundation/nuts-node:master}" | |||
image: "${IMAGE_NODE_A:-nutsfoundation/nuts-node:latest}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
image: "${IMAGE_NODE_A:-nutsfoundation/nuts-node:latest}" | |
image: "${IMAGE_NODE_A:-nutsfoundation/nuts-node:master}" |
@@ -25,7 +25,7 @@ services: | |||
- "../../tls-certs/truststore.pem:/etc/nginx/ssl/truststore.pem:ro" | |||
- "./node-A/html:/etc/nginx/html:ro" | |||
nodeB: | |||
image: "${IMAGE_NODE_B:-nutsfoundation/nuts-node:master}" | |||
image: "${IMAGE_NODE_B:-nutsfoundation/nuts-node:latest}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
image: "${IMAGE_NODE_B:-nutsfoundation/nuts-node:latest}" | |
image: "${IMAGE_NODE_B:-nutsfoundation/nuts-node:master}" |
Add to OpenAPI web epxlorer? |
closes #2629
I described that removing a service does not have any influence on services referencing that service. Other than that everything is just basic CRUD.
One of those PRs where it takes more time to review than to make ;)