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

Nested lazy find with secondary ref #17425

Merged
merged 8 commits into from
May 16, 2018

Conversation

Ladas
Copy link
Contributor

@Ladas Ladas commented May 15, 2018

Nested lazy find with secondary ref. Allowing to pass option, that will transform all nested InventoryObjectLazy into InventoryObject, allowing us to use nested InventoryObjectLazy with secondary references

Ladas added 8 commits May 11, 2018 14:08
Check if reference contains only references to primary indexes inside
Assert we build InventoryObject only with references to primary index
…ill fail

Test that secondary reference, used for InventoryObject manager ref will fail
Transform nested references with secondary index on load
Test nested references with secondary index work
Add guard for nested references being too deep
Make nested lazy finds explicit for now, before we are able to
transform it automatically, when needed.
Test explicit transform_nested_lazy_finds
@Ladas
Copy link
Contributor Author

Ladas commented May 15, 2018

@miq-bot add_label enhancement
@miq-bot assign @agrare

@miq-bot
Copy link
Member

miq-bot commented May 15, 2018

Checked commits Ladas/manageiq@b5f8585~...d1405c2 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
7 files checked, 3 offenses detected

app/models/manager_refresh/inventory_object_lazy.rb

spec/models/manager_refresh/persister/finders_spec.rb

@agrare agrare merged commit c5ba7e8 into ManageIQ:master May 16, 2018
@jrafanie jrafanie added this to the Sprint 86 Ending May 21, 2018 milestone May 22, 2018
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.

4 participants