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

Add ext_management_system.id to Migration Readiness summary reports #18944

Merged

Conversation

mturley
Copy link
Contributor

@mturley mturley commented Jul 8, 2019

As part of the new Migration Analytics plugin that I am working on (https://github.com/mturley/cfme-migration_analytics), I need to consume the two Migration Readiness reports that were made available in #18749 to display the summary data required for https://bugzilla.redhat.com/show_bug.cgi?id=1708369.

I need to correlate the results of these two reports with other data from the ManageIQ API based on the ext_management_system.id column, which is not present in these reports. I could use ext_management_system.name, but that assumes the user has not created two providers with the same name, which is technically possible.

This PR adds the id field to these two reports so I can make a more robust relation with other ext_management_system API data.

@Fryguy Fryguy self-assigned this Jul 8, 2019
@Fryguy Fryguy added this to the Sprint 115 Ending Jul 8, 2019 milestone Jul 8, 2019
@djberg96
Copy link
Contributor

djberg96 commented Jul 8, 2019

👍

@miq-bot
Copy link
Member

miq-bot commented Jul 8, 2019

Checked commits mturley/manageiq@3cb9d9e~...8f143fb with ruby 2.4.6, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0
0 files checked, 0 offenses detected
Everything looks fine. 🏆

@Fryguy Fryguy merged commit 5a73824 into ManageIQ:master Jul 8, 2019
@pemcg
Copy link

pemcg commented Jul 9, 2019

LGTM

@mturley mturley deleted the migration-readiness-reports-provider-id branch July 9, 2019 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants