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.

Sign up for GitHub

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

Jump to bottom

DRS + Passports versioning #354

Open
jb-adams opened this issue Apr 28, 2021 · 0 comments
Open

DRS + Passports versioning #354

jb-adams opened this issue Apr 28, 2021 · 0 comments
Labels
Priority: High Project: DRS Type: Enhancement

Comments

@jb-adams
Copy link
Member

jb-adams commented Apr 28, 2021 •
edited by unito-bot
Loading

A sub-problem of the DRS + Passports Design Resolution epic.

This sub-problem involves reaching consensus on how to capture payload/flow version information throughout the API call flow to enable clients a mechanism for achieving backward and forward compatibility.

Questions include:

  • Where should versioning of the DRS/Passport API be? Should it be captured in the:
    • Payload?
    • REST API URL path?
    • DRS service-info endpoint?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority: High Project: DRS Type: Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jb-adams