Automatic decommission #14

Open
opened 2019-08-05 17:35:58 +02:00 by ramnes · 1 comment
ramnes commented 2019-08-05 17:35:58 +02:00 (Migrated from github.com)

For those that always want their Netbox 100% up-to-date, a cron-mode could be provided so that every agent fills in a last update date while another mechanism on the Netbox-side would be in charge of removing expired resources.

For those that always want their Netbox 100% up-to-date, a cron-mode could be provided so that every agent fills in a last update date while another mechanism on the Netbox-side would be in charge of removing expired resources.
Solvik commented 2019-08-05 17:52:08 +02:00 (Migrated from github.com)

Netbox has attribute on Device to see when was the last update
But if there's no local modifications (IPs, new hardware etc) it won't be updated

I see two ways:

  • we could add a last_cron_update in the JSON Config Context but there is now way to filter on configcontext value
  • the other way is to use a CustomField, it's searchable but it needs to be created on the user's netbox instance
Netbox has attribute on Device to see when was the last update But if there's no local modifications (IPs, new hardware etc) it won't be updated I see two ways: - we could add a `last_cron_update` in the JSON Config Context but there is now way to filter on configcontext value - the other way is to use a CustomField, it's searchable but it needs to be created on the user's netbox instance
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: DGNum/netbox-agent#14
No description provided.