nautobot-app-golden-config
nautobot-app-golden-config copied to clipboard
Delete All config compliance objects doesn't work
Environment
- Python version: 3.8.6
- Nautobot version: 1.3.7
- nautobot-golden-config version: 1.0.3
Steps to Reproduce
- Generate 26+ configuration compliance entries in the "Configuration Compliance" page/table
- Change your table view to be 25 items at a time
- Hit the check box to select all items on the page
- In the new selection that appears, select "Select all ### config compliances matching query"
- Click the "Delete All" button
Expected Behavior
The confirmation page prompting me to delete all entries should appear. Note: This works when selecting multiple entries on a single page.
Observed Behavior
The below warning banner appears, and the page refreshes, without prompting me to confirm object deletion:
"No config compliances were selected for deletion."
It should also be noted that this is limited to the "Delete All" button. Selecting <1000 items, and selecting "Delete" at the bottom of the page, will work as expected as long as all items are on the same visible page.
Is this different than nautobot? If not, likely to fall into “works as expected”
@itdependsnetworks This works correctly on other core Nautobot pages, such as "Devices"
Are you saying this doesn't show up? like this:
![image](https://user-images.githubusercontent.com/9260483/185747608-852f953b-f31a-4e1d-84a0-ed69ee96ee4b.png)
Not quite. On the plug-in, the button shows up. But when you click on it, the page refreshes and nothing happens.
On other core Nautobot pages, it loads an "Are you sure?" page.
Are the above replication steps not working correctly?
@jeffkala to take a look at recreating in his env
Can duplicate on demo.nautobot.com, it actually pops up with delete all 389 objects, you click the button and the next plage actually only loads the first object and says are you sure, folowed by not deleting it at all.
@matt852 what would you expect for this? To just have it reload back to having now "last" dates? This view is actually populated based on the device list. An actual object isn't even created until a backup/intended etc has been run on that device.
Fixed in #353