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

Cleanup Profile Resolution Endpoints #81

Closed
2 tasks done
Tracked by #82
brian-ruf-ezd opened this issue Feb 13, 2024 · 2 comments
Closed
2 tasks done
Tracked by #82

Cleanup Profile Resolution Endpoints #81

brian-ruf-ezd opened this issue Feb 13, 2024 · 2 comments
Assignees
@mpemy

Comments

@brian-ruf-ezd
Copy link
Contributor

brian-ruf-ezd commented Feb 13, 2024 •
edited
Loading

There are two sets of endpoints related to profile resolution:

  • resolved-catalog; and
  • resolved-snapshot

The resolved-catalog endpoints are intended for point-in-time processing and do not persist any information.
For this reason, the only valid method/endpoint is: GET /profile/{Identifier}/resolved-catalog

This should immediately resolve the profile into a catalog and return the result.

The PUT and PATCH methods incorrectly exist for resolved-catalog.

The following actions are required:

  • Eliminate PUT /profile/{Identifier}/resolved-catalog
  • Eliminate PATCH /profile/{Identifier}/resolved-catalog
@brian-ruf-ezd brian-ruf-ezd mentioned this issue Feb 13, 2024
Closed
@brian-ruf-ezd
Copy link
Contributor Author

Per Issue #87 we are eliminating PATCH throughout the spec. Ignore any reference to PATCH here.

@brian-ruf-ezd
Copy link
Contributor Author

This is addressed in PR #72.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mpemy mpemy

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mpemy @brian-ruf-ezd