-
Notifications
You must be signed in to change notification settings - Fork 20
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
feat: Add client for SystemLink products API #69
Conversation
nisystemlink/clients/testmonitor/models/_delete_products_partial_success.py
Outdated
Show resolved
Hide resolved
nisystemlink/clients/testmonitor/models/_query_products_request.py
Outdated
Show resolved
Hide resolved
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.
During the planning for Grafana plugins for Test Monitor, there was a discussion of if we should have one "Test Monitor" plugin or separate plugins for products, test results, etc. The consensus was that Products should be its own plugin, because that's the way our customers understand SystemLink. The fact that it's one microservice is an implementation detail. Should we apply the same logic here and have a ProductClient
?
nisystemlink/clients/testmonitor/models/_create_products_request.py
Outdated
Show resolved
Hide resolved
nisystemlink/clients/testmonitor/models/_query_products_request.py
Outdated
Show resolved
Hide resolved
@mure I like the idea of having a |
… have room for the generator pattern
What does this Pull Request accomplish?
This PR adds client methods for all of the
nitestmonitor
product endpoints as well as testing for these endpoints.Why should this Pull Request be merged?
This is an enhancement to the existing test monitor client and will enable users to more easily interact with SystemLink products.
What testing has been done?
Auto testing is included against NI's test tier.