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

Refactor/anoncreds revocation move logic #124

Conversation

cjhowland
Copy link

This PR updates the /anoncreds/revocation-registry-definition and /anoncreds/revocation-list endpoints to call corresponding methods on AnonCredsIssuer rather than IssuerRevRegRecord.

…nCredsIssuer

Signed-off-by: Char Howland <char@indicio.tech>
…AnonCredsIssuer

Signed-off-by: Char Howland <char@indicio.tech>
Signed-off-by: Char Howland <char@indicio.tech>
Comment on lines -508 to +512
issuer_id: str,
cred_def_id: str,
registry_type: str,
tag: str,
max_cred_num: int,
profile,
issuer_rev_reg_record: IssuerRevRegRecord,
Copy link
Member

Choose a reason for hiding this comment

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

Could you help me understand the motivation for passing the issuer rev reg record instead of the individual components of issuer_id, cred_def_id, etc.?

Copy link
Author

Choose a reason for hiding this comment

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

My motivation was that if we pass in the whole record, we can access the components that aren't directly passed in (_id, state) that previously we didn't have to pass in because the method was on the IssuerRevRegRecord itself. This seemed preferrable to adding _id and state to be retrieved from the request body and passed directly into AnonCredsIssuer.create_and_register_revocation_registry_definition(). Curious to hear your thoughts and other alternatives.

Signed-off-by: Char Howland <char@indicio.tech>
@dbluhm
Copy link
Member

dbluhm commented Dec 6, 2023

Stale and no longer relevant. Closing!

@dbluhm dbluhm closed this Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants