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

[v2] Separate proposed input types from the type-specific schemas #1305

Open
asraa opened this issue Jan 27, 2023 · 0 comments
Open

[v2] Separate proposed input types from the type-specific schemas #1305

asraa opened this issue Jan 27, 2023 · 0 comments
Labels
enhancement New feature or request rekor-v2

Comments

@asraa
Copy link
Contributor

asraa commented Jan 27, 2023

Description

Clients should allow sending proposed entries as non strongly types entries, something like the following:

ProposedEntry:

type: intoto
pk: pk
etc...

that includes the proposed type it intends to be. Rekor server-side should create the type specific entry.

This would provide clarity in the required fields of the server-side computed entries, and allow clients to not have to deal with type specific canonicalization.

I think search, create, retrieve should all use this type of input data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request rekor-v2
Projects
None yet
Development

No branches or pull requests

2 participants