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

[Spike] Management API: investigate path multiplexing mechanisms #4183

Open
Tracked by #4180
paullatzelsperger opened this issue May 15, 2024 · 1 comment
Open
Tracked by #4180
Labels
stale Open for x days with no activity triage all new issues awaiting classification

Comments

@paullatzelsperger
Copy link
Member

paullatzelsperger commented May 15, 2024

Not every controller of the API changes on every version bump, so we may need to make the same controller available under multiple paths.

Here evaluate different path multiplexing approaches (custom interceptor vs simply duplicating the controller classes) with special attention to the following aspects:

  • will both (old and new) controllers be represented in the generated openapi document?
  • how easy/straight-forward is it to introduce a new major version of the API?
  • how easy/straight-forward is it to remove a deprecated version of the API?
@github-actions github-actions bot added the triage all new issues awaiting classification label May 15, 2024
@paullatzelsperger paullatzelsperger changed the title spike: evaluate different path multiplexing approaches (custom interceptor vs simply duplicating the controller classes) [Spike] Management API: investigate path multiplexing mechanisms May 15, 2024
Copy link

This issue is stale because it has been open for 14 days with no activity.

@github-actions github-actions bot added the stale Open for x days with no activity label May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Open for x days with no activity triage all new issues awaiting classification
Projects
None yet
Development

No branches or pull requests

1 participant