-
Notifications
You must be signed in to change notification settings - Fork 81
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
Servicenow inventory relations #108
Comments
Enhanced grouping depends on a custom scripted API endpoint. In other words, enhanced grouping is only available if the ServiceNow instance has a proper update set applied. Apart from that, there are no technical limitations about this issue, just time constraints ;) |
Is this feature available if we install the Update Set? Is there documentation on it? |
If you apply the update set, inventory relations become available through the API, but the current version of the plugin does not know how to handle that data. The inventory plugin from the servicenow.servicenow collection can use this data, but I must admit that I never used it and cannot tell you how the results look like. |
Thank you for that clarification @tadeboro :) What would be needed to implement this handling? Maybe I would be able to contribute the new feature with some guidance. |
Remove assumed /api/now base path from the HTTP client SUMMARY ServiceNow Update Sets allow for extending the functionality of ServiceNow by, for example, obtaining and formatting results from joined tables. Through the ServiceNow REST API the records from Update Sets can be programmatically obtained. Currently, in the HTTP client it is assumed that all API endpoints start with base path /api/now, which might not be true in case of Updated Sets or in general when the requests might refer to the records outside namespace now. This update removes the assumption about the base URL path from the HTTP client, by accepting any path, which makes it more generic. While it does not directly address any issue, it shall be seen as a prerequisite to issue #108, the resolution of which can be done by using a particular Updated Set, which is accessible on URL path starting with /api/snc. ISSUE TYPE Feature Pull Request (a prerequisite to) COMPONENT NAME This update does not introduce any new components. ADDITIONAL INFORMATION The primary target of this update is request method of class Client, located in file plugins/module_utils/client.py, where the base path is changed to "/". Consequentially, all the code relying upon the request method, either directly or indirectly, is affected. Accordingly, the TableClient and AttachmentClient have been updated. The unit tests for Client, TableClient and AttachmentClient have also been adapted to the change in the base URL path. Reviewed-by: Tadej Borovšak <None> Reviewed-by: Abhijeet Kasurde <None> Reviewed-by: None <None>
Enhance inventory with groups from CMDB relations SUMMARY Extends inventory plugin module with groups extracted from CMDB relations. Addresses issue #108. ISSUE TYPE Feature Pull Request COMPONENT NAME Changes to now, added relations module utilities. ADDITIONAL INFORMATION To enable this extension, add option enhanced: true to the inventory file. Unlike the implementation from the old, deprecated repository, which required installation of an update set, this implementation obtains all the required data through ServiceNow REST API. Reviewed-by: Abhijeet Kasurde <None> Reviewed-by: None <None>
@hugotomasi @Razican Can I close this issue? |
I'm closing this issue. It has been solved in #143. |
SUMMARY
Hello,
I was wondering if there was any future plan in this development to enable the use of relations. What would be great would be to be able to get a field that was only specified in a relation.
I may be wrong but I believe there was a "try" in the other repository about enhanced groups.
Thanks in advance for your kind replies :)
ISSUE TYPE
COMPONENT NAME
Relations browsing feature
The text was updated successfully, but these errors were encountered: