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

Consolidate verification response between configPolicy and regoPolicy #1690

Open
1 task
binbin-li opened this issue Aug 6, 2024 · 0 comments
Open
1 task
Labels
enhancement New feature or request
Milestone

Comments

@binbin-li
Copy link
Collaborator

What would you like to be added?

Currently we have 2 versions for verification response, 0.1.0 is used for configPolicy engine while 1.0.0 is for regoPolicy.
Since 2 versions are incompatible, we need to maintain both of them for configPolicy and regoPolicy engines. To reduce confusion from users, we need to take some actions:

  1. Clarify the user scenarios and comparison in document.
  2. Deprecate configPolicy or refactor the configPolicy engine to fix existing bugs. Fix Config Policy Provider for Nested References #351, feat: multiple signatures verification #737, Decouple nested references from verifiers #528
  3. Switch the response version adopted by configPolicy or regoPolicy in V2 so that all policy engines could evaluate the verifierReport.

Anything else you would like to add?

No response

Are you willing to submit PRs to contribute to this feature?

  • Yes, I am willing to implement it.
@binbin-li binbin-li added enhancement New feature or request triage Needs investigation labels Aug 6, 2024
@binbin-li binbin-li added this to the Future milestone Aug 8, 2024
@binbin-li binbin-li removed the triage Needs investigation label Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant