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

Create a replacement for the status check router in the new system and deprecated it from the commons #24548

Open
3 tasks
Tracked by #24493
camilaibs opened this issue Apr 29, 2024 · 0 comments · May be fixed by #24817
Open
3 tasks
Tracked by #24493
Assignees
Labels
area:core Related to the Core Backstage Framework backend

Comments

@camilaibs
Copy link
Contributor

Context

Ref: #24493

In preparation for the new backend system stable release, we will deprecate the backend-common package.

Description

The createStatusCheckRouter is currently exported from the backend-common package and should be converted to something compatible with the new backend system as we are going to get rid of the common package. As it is essentially used for health checks, perhaps a backend plugin could expose the router endpoints over HTTP.

Open questions

Is this an endpoint per plugin?

Suggested Approach

  • Understand how legacy backends currently use it
  • Consider adding this by default to each plugin in the core framework
  • Explore other alternatives, propose and implement a solution
@camilaibs camilaibs added backend area:core Related to the Core Backstage Framework labels Apr 29, 2024
@vinzscam vinzscam linked a pull request May 17, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:core Related to the Core Backstage Framework backend
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants