-
Notifications
You must be signed in to change notification settings - Fork 42
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
Targeted refresh for NetworkPorts #111
Conversation
@@ -71,7 +78,7 @@ | |||
|
|||
describe "on empty database" do | |||
it "will refresh cloud_subnet" do | |||
cloud_subnet = FactoryGirl.build(:cloud_subnet_nuage, :ems_ref => cloud_subnet_ref1) | |||
cloud_subnet = FactoryGirl.build(:cloud_subnet_l3_nuage, :ems_ref => cloud_subnet_ref1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so here, :ext_management_system is missing. Has to be filled everywhere, if the table has :ems_id column
8b84514
to
ba397e1
Compare
Checked commits miha-plesko/manageiq-providers-nuage@3f72ac9~...ba397e1 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
This pull request is not mergeable. Please rebase and repush. |
With this commit we implement targeted refresh for NetworkPort. Signed-off-by: Miha Pleško <[email protected]>
ba397e1
to
f951388
Compare
@Ladas this PR concludes targeted refresh backend. Then we only need the AE Instance in miq-content to make sure it's triggered plus the memoization followup PR as discussed on gitter. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 great
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great 👍
What title says ^
RFE BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1574940