Skip to content
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

Discovery: update client copy of Discovery Services #2718

Merged
merged 12 commits into from
Jan 22, 2024

Conversation

reinkrul
Copy link
Member

@reinkrul reinkrul commented Jan 10, 2024

Requires #2730

@reinkrul reinkrul force-pushed the discovery/update-clients branch from 627259c to ce6ee81 Compare January 11, 2024 05:53
@reinkrul reinkrul marked this pull request as ready for review January 11, 2024 05:53
@reinkrul reinkrul force-pushed the discovery/update-clients branch from e506d89 to d669239 Compare January 11, 2024 09:48
Copy link
Member

@gerardsn gerardsn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Im starting to get a bit lost in the naming in the discovery service. It not obvious to me how to map the roles/responsibilities to the individual objects.

@@ -33,5 +33,7 @@ func FlagSet() *pflag.FlagSet {
flagSet.StringSlice("discovery.server.definition_ids", defs.Server.DefinitionIDs,
"IDs of the Discovery Service Definitions for which to act as server. "+
"If an ID does not map to a loaded service definition, the node will fail to start.")
flagSet.Duration("discovery.client.update_interval", defs.Client.UpdateInterval, "How often to check for Discovery Services updates, "+
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

difference between this and registration_refresh_interval would be a lot clearer if description starts with the key difference. e.g., "(Re-)Publish at this interval" and "Fetch updates at this interval".

discovery/interface.go Outdated Show resolved Hide resolved
discovery/config.go Outdated Show resolved Hide resolved
discovery/client.go Outdated Show resolved Hide resolved
@reinkrul
Copy link
Member Author

Im starting to get a bit lost in the naming in the discovery service. It not obvious to me how to map the roles/responsibilities to the individual objects.

What if I renamed "registration" on the client-side "activation"? So XIS admin apps call activateDID(did, service) and deactivateDID(did, service), then the Discovery Client registers a Verifiable Presentation on the Discovery Service?

discovery/module.go Outdated Show resolved Hide resolved
discovery/client.go Show resolved Hide resolved
e2e-tests/discovery/run-test.sh Outdated Show resolved Hide resolved
e2e-tests/discovery/run-test.sh Outdated Show resolved Hide resolved
@reinkrul reinkrul dismissed gerardsn’s stale review January 22, 2024 09:10

verything adressed

@reinkrul reinkrul merged commit 87a6283 into master Jan 22, 2024
9 checks passed
@reinkrul reinkrul deleted the discovery/update-clients branch January 22, 2024 09:10
rolandgroen added a commit that referenced this pull request Jan 25, 2024
* master: (38 commits)
  VDR: Fix duplicate results when listing DIDs (#2743)
  VDR: API to list owned DIDs (#2742)
  VDR: Move did:nuts specific to did:nuts creator (#2735)
  Discovery: API to list configured Discovery Services (#2739)
  PKI: Adjust validation logging; OK = trace, NOK = info (#2736)
  Discovery: update client copy of Discovery Services (#2718)
  VDR: Group all DID Document management funcs in a new interface (#2737)
  Handle direct_post return from wallet to verifier (#2702)
  Bump github.com/nats-io/nats.go from 1.31.0 to 1.32.0 (#2724)
  Discovery: fix API of Client.Search() (#2730)
  Bump github.com/amacneil/dbmate/v2 from 2.10.0 to 2.11.0 (#2729)
  Discovery: DID registration by clients (#2709)
  Config: Add HTTP-client timeout (#2725)
  Policy: prevent nil dereference when no backend is configured (#2723)
  Bump github.com/nats-io/nats-server/v2 from 2.10.7 to 2.10.9 (#2721)
  SQL: specify lengths for VARCHAR columns to avoid different behavior with different RDBMS's (#2717)
  Bump golang from 1.21.5-alpine to 1.21.6-alpine (#2719)
  Handle authorization request from verifier by holder/wallet (#2680)
  Bump golang.org/x/crypto from 0.17.0 to 0.18.0 (#2716)
  Bump github.com/lestrrat-go/jwx/v2 from 2.0.18 to 2.0.19 (#2715)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants