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

Fixes #32782 - Add types and queries for Lookup Values #8585

Merged
merged 1 commit into from
Jun 29, 2021

Conversation

xprazak2
Copy link
Contributor

No description provided.

@theforeman-bot
Copy link
Member

Issues: #32782

Copy link
Member

@ezr-ondrej ezr-ondrej left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This make sense and I'm ok with that as it is definitelly a way forward, though I'm not sure this include inherited values. Or does it?
Do we even want that?

Can we add such values in test (ie on OS for the HG) and explicitly expect them to be there or not, so we know in the future how it was supposed to behave?

@xprazak2
Copy link
Contributor Author

I added a test case where matcher is a value for child hostgroup, but I do not think inheritance is relevant here. Query for single record fetches lookup value by id and query for collection fetches a collection and ou can always use search to filter the results.

Copy link
Member

@ezr-ondrej ezr-ondrej left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right until we support resource's lookup values (i.e. host's values) the inheritance is irrelevant.

@ezr-ondrej ezr-ondrej merged commit 9111722 into theforeman:develop Jun 29, 2021
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.

3 participants