-
Notifications
You must be signed in to change notification settings - Fork 29
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
Feature - Per Tenant Validated Software Report #341
Comments
I like this idea. We should also add some way of informing the user on the date/time each result was generated. |
I believe this will get fixed with recently submitted PR: #397 |
"I like this idea. We should also add some way of informing the user on the date/time each result was generated." Just realized this was here, will work on this update. |
After further discussion, the ability to see the Date/Time for each device on the current result is already available via the Device Software Validation Report now that the job can target devices individually. What we are looking for is a historical way to see what filtered/full request was contained in a job run. Something similar to the SSoT historical sync records. |
Environment
Proposed Functionality
The ability to run a validated software report per tenant.
Use Case
Nautobot instances with multiple tenants may have need to run validation on a specific tenant.
UC 1:
Tenant 1 has 4000 devices
Tenant 2 has 25
Tenant 2 has to wait 2 hours for the report to run just to see the state of their 25 devices.d
UC 2:
Instance has 20 tenants, most with 300 devices.
All tenants have to wait 2-3+ hours to get the report that could have taken much less time.
The text was updated successfully, but these errors were encountered: