-
Notifications
You must be signed in to change notification settings - Fork 357
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
Discovery names to be relocated to other repo(s) #2529
Comments
This issue has been automatically marked as stale because it has not been updated for at least 6 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! |
@gildub is this still a valid issue? If yes, lease remove the stale label. If not can you close. |
@JPrause, well I'm not sure who's going to work on that one, not a blocker but such coupling is bad on the long term. |
This issue has been automatically marked as stale because it has not been updated for at least 6 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! |
related to ManageIQ/manageiq#19440 cc @agrare |
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation. |
Added as a checklist item to ManageIQ/manageiq#19440 |
I believe the list of discovery types in [1] to be relocated to https://github.com/ManageIQ/manageiq.
The first reason is to be DRY as part of that information is also defined in [2] although more consolidation would be needed. Another driver would for future UI modularity.
Ultimately such meta data information might be better living under their respective providers.
[1] https://github.com/ManageIQ/manageiq-ui-classic/blob/master/app/helpers/application_helper/discover.rb#L4-L17
[2] https://github.com/ManageIQ/manageiq/blob/master/app/models/host.rb#L15-L23
The text was updated successfully, but these errors were encountered: