-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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: Unregister runtime artifacts #2619
Comments
We now have the infrastructure in place, such as |
We also need to find out which artifacts may have impacts when they are changed. It also has something to do with binding scopes. |
Yes. Removing a controller must remove the REST API endpoints too.
I think different artifacts may need different approach. For example, there may be very little work needed to unregister a model class. On the other hand, removing a controller is more involved, as we have to update the routing table. It may be better to split this spike into smaller tasks, for example:
I think we need to take into account dependencies between artifacts too. For example, it does not make sense to unregister a Repository class when there are controllers still using it. In the first iteration, I am fine to leave it up to developers to ensure they unregister all artifact types. We can investigate more robust solutions later. The key requirements for the first iteration:
|
This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the |
This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the |
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the |
Description / Steps to reproduce / Feature proposal
Spike for #2485
Investigate on how to unbind/unregister LB artifacts:
Questions:
The text was updated successfully, but these errors were encountered: