forward-netbox 2.4.2__tar.gz → 2.4.3__tar.gz

{forward_netbox-2.4.2 → forward_netbox-2.4.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: forward-netbox
-Version: 2.4.2
+Version: 2.4.3
 Summary: NetBox plugin to sync Forward data into NetBox via built-in NQE queries
 License: MIT
 License-File: LICENSE
@@ -99,7 +99,8 @@ Latest release requires NetBox `4.6.4` and `netbox-branching` `1.1.0+`. Expand f
 
 | Plugin Release | NetBox Version | Status |
 | --- | --- | --- |
-| `v2.4.2` | `4.6.4` required; needs netbox-branching `1.1.0+` | Current release; Fix: endpoint import (`sync_endpoints`) and device-tag sync (`sync_device_tags`) now work with the alias-aware and rules-aware query variants (`forward_devices_with_netbox_aliases`, `forward_device_feature_tags_with_rules`), not just the base queries — operators running the variants saw the toggles silently do nothing (validated live: 355 Avocent endpoints import; `Mgmt_*` tags sync). Adds a **Publish Bundled Queries** button on the sync Health page (beside Refresh Query IDs) and two Health warnings: when an opt-in feature is enabled but no enabled map provides it, and when a base query and its opt-in variant are both enabled (they double-apply rows for the same model and churn — enable one). The alias-aware device query now emits the clean role name (e.g. `ROUTER`) to match the base query — expect a one-time role update on alias-mapped devices. |
+| `v2.4.3` | `4.6.4` required; needs netbox-branching `1.1.0+` | Current release; Fix: the pinned-query opt-in Health warning (2.4.1) over-claimed failure — it reads "nothing new syncs" and fires on any pinned map with the feature on, even after the query is fixed, because the Health page can't read a pinned query's contents. Reworded to a "Pinned — can't verify locally" heads-up that points at **Export Live Query Drift** to confirm (`source_matches_bundled`), instead of asserting failure. No behavior change. |
+| `v2.4.2` | `4.6.4` required; needs netbox-branching `1.1.0+` | Superseded by `v2.4.3`; Fix: endpoint import (`sync_endpoints`) and device-tag sync (`sync_device_tags`) now work with the alias-aware and rules-aware query variants (`forward_devices_with_netbox_aliases`, `forward_device_feature_tags_with_rules`), not just the base queries — operators running the variants saw the toggles silently do nothing (validated live: 355 Avocent endpoints import; `Mgmt_*` tags sync). Adds a **Publish Bundled Queries** button on the sync Health page (beside Refresh Query IDs) and two Health warnings: when an opt-in feature is enabled but no enabled map provides it, and when a base query and its opt-in variant are both enabled (they double-apply rows for the same model and churn — enable one). The alias-aware device query now emits the clean role name (e.g. `ROUTER`) to match the base query — expect a one-time role update on alias-mapped devices. |
 | `v2.4.1` | `4.6.4` required; needs netbox-branching `1.1.0+` | Superseded by `v2.4.2`; Fix: opt-in features (SNMP endpoint import, device-tag sync) silently did nothing on sources that run org-managed **pinned** Forward query IDs predating the feature — the sync Health page now raises an actionable warning instead of a silent badge. Remediation: publish the bundled queries to your Forward org folder (Overwrite on), then use Refresh Query IDs, then re-sync. |
 | `v2.4.0` | `4.6.4` required; needs netbox-branching `1.1.0+` | Superseded by `v2.4.1`; Fix: the "Import SNMP Endpoints as Devices" toggle now renders on the source form (the field shipped in 2.3.2 but was not in any fieldset, so it never showed), letting operators enable endpoint import from the GUI. |
 | `v2.3.2` | `4.6.4` required; needs netbox-branching `1.1.0+` | Superseded by `v2.4.0`; Feature: optional import of Forward SNMP endpoints (e.g. Avocent console servers) as NetBox devices — off by default (`sync_endpoints`), enabled per source and scoped by the same device tags. |

{forward_netbox-2.4.2 → forward_netbox-2.4.3}/README.md

@@ -66,7 +66,8 @@ Latest release requires NetBox `4.6.4` and `netbox-branching` `1.1.0+`. Expand f
 
 | Plugin Release | NetBox Version | Status |
 | --- | --- | --- |
-| `v2.4.2` | `4.6.4` required; needs netbox-branching `1.1.0+` | Current release; Fix: endpoint import (`sync_endpoints`) and device-tag sync (`sync_device_tags`) now work with the alias-aware and rules-aware query variants (`forward_devices_with_netbox_aliases`, `forward_device_feature_tags_with_rules`), not just the base queries — operators running the variants saw the toggles silently do nothing (validated live: 355 Avocent endpoints import; `Mgmt_*` tags sync). Adds a **Publish Bundled Queries** button on the sync Health page (beside Refresh Query IDs) and two Health warnings: when an opt-in feature is enabled but no enabled map provides it, and when a base query and its opt-in variant are both enabled (they double-apply rows for the same model and churn — enable one). The alias-aware device query now emits the clean role name (e.g. `ROUTER`) to match the base query — expect a one-time role update on alias-mapped devices. |
+| `v2.4.3` | `4.6.4` required; needs netbox-branching `1.1.0+` | Current release; Fix: the pinned-query opt-in Health warning (2.4.1) over-claimed failure — it reads "nothing new syncs" and fires on any pinned map with the feature on, even after the query is fixed, because the Health page can't read a pinned query's contents. Reworded to a "Pinned — can't verify locally" heads-up that points at **Export Live Query Drift** to confirm (`source_matches_bundled`), instead of asserting failure. No behavior change. |
+| `v2.4.2` | `4.6.4` required; needs netbox-branching `1.1.0+` | Superseded by `v2.4.3`; Fix: endpoint import (`sync_endpoints`) and device-tag sync (`sync_device_tags`) now work with the alias-aware and rules-aware query variants (`forward_devices_with_netbox_aliases`, `forward_device_feature_tags_with_rules`), not just the base queries — operators running the variants saw the toggles silently do nothing (validated live: 355 Avocent endpoints import; `Mgmt_*` tags sync). Adds a **Publish Bundled Queries** button on the sync Health page (beside Refresh Query IDs) and two Health warnings: when an opt-in feature is enabled but no enabled map provides it, and when a base query and its opt-in variant are both enabled (they double-apply rows for the same model and churn — enable one). The alias-aware device query now emits the clean role name (e.g. `ROUTER`) to match the base query — expect a one-time role update on alias-mapped devices. |
 | `v2.4.1` | `4.6.4` required; needs netbox-branching `1.1.0+` | Superseded by `v2.4.2`; Fix: opt-in features (SNMP endpoint import, device-tag sync) silently did nothing on sources that run org-managed **pinned** Forward query IDs predating the feature — the sync Health page now raises an actionable warning instead of a silent badge. Remediation: publish the bundled queries to your Forward org folder (Overwrite on), then use Refresh Query IDs, then re-sync. |
 | `v2.4.0` | `4.6.4` required; needs netbox-branching `1.1.0+` | Superseded by `v2.4.1`; Fix: the "Import SNMP Endpoints as Devices" toggle now renders on the source form (the field shipped in 2.3.2 but was not in any fieldset, so it never showed), letting operators enable endpoint import from the GUI. |
 | `v2.3.2` | `4.6.4` required; needs netbox-branching `1.1.0+` | Superseded by `v2.4.0`; Feature: optional import of Forward SNMP endpoints (e.g. Avocent console servers) as NetBox devices — off by default (`sync_endpoints`), enabled per source and scoped by the same device tags. |

{forward_netbox-2.4.2 → forward_netbox-2.4.3}/forward_netbox/__init__.py

@@ -8,7 +8,7 @@ class NetboxForwardConfig(PluginConfig):
     name = "forward_netbox"
     verbose_name = "Forward"
     description = "Sync Forward data into NetBox using built-in NQE queries."
-    version = "2.4.2"
+    version = "2.4.3"
     base_url = "forward"
     min_version = "4.6.4"
 

{forward_netbox-2.4.2 → forward_netbox-2.4.3}/forward_netbox/tests/test_endpoints_import.py

@@ -74,9 +74,13 @@ class OptInPinnedDriftElevationTest(SimpleTestCase):
         self.assertEqual(drift[0]["severity"], "warn")
         self.assertEqual(drift[0]["status"], "direct_query_id_optin_stale_risk")
         self.assertIn("Refresh Query IDs", drift[0]["remediation"])
+        # Wording is a "can't verify locally" heads-up pointing at the live
+        # check, not a confirmed failure.
+        self.assertIn("Live Query Drift", drift[0]["remediation"])
+        self.assertIn("can't inspect locally", drift[0]["message"])
         # Badge label must track the elevated status, not the stale build-time one.
         self.assertNotEqual(drift[0].get("status_label"), "Org-managed (pinned)")
-        self.assertIn("predate", drift[0].get("status_label", ""))
+        self.assertIn("verify", drift[0].get("status_label", ""))
 
     def test_endpoints_disabled_leaves_pinned_device_query_silent(self):
         drift = [self._pinned("forward_devices.nqe")]

{forward_netbox-2.4.2 → forward_netbox-2.4.3}/forward_netbox/utilities/health.py

@@ -136,17 +136,23 @@ def _elevate_optin_pinned_query_drift(query_drift, source_parameters):
         # stale "Org-managed (pinned)" badge on the elevated row.
         item["status_label"] = _QUERY_DRIFT_STATUS_LABELS.get(
             "direct_query_id_optin_stale_risk",
-            "Pinned — may predate an enabled feature",
+            "Pinned — can't verify locally",
         )
         item["severity"] = "warn"
+        # This is a "can't verify locally" heads-up, not a confirmed failure:
+        # the Health page can't read a pinned query's contents, so it warns for
+        # any pinned map with the feature on — including one that's already
+        # current after publishing. Point at the live check, don't claim failure.
         item["message"] = (
-            f"“{label}” is enabled, but this map runs a pinned Forward query ID. "
-            "If that query predates the feature it is silently ignored, so "
-            "nothing new syncs."
+            f"“{label}” is enabled and this map runs a pinned Forward query ID, "
+            "which the Health page can't inspect locally to confirm it includes "
+            "the feature. If those rows aren't importing, the pinned query may "
+            "predate the feature."
         )
         item["remediation"] = (
-            "Publish the bundled queries to your Forward org folder (Overwrite "
-            "on), then use Refresh Query IDs on this Health page, then re-run the "
+            "Use Export Live Query Drift on this page to confirm the pinned "
+            "query matches the current bundled source. If it doesn't, use "
+            "Publish Bundled Queries, then Refresh Query IDs, then re-run the "
             "sync."
         )
         item["remediation_action"] = "refresh_query_ids"

{forward_netbox-2.4.2 → forward_netbox-2.4.3}/forward_netbox/utilities/query_binding_resolution.py

@@ -436,7 +436,7 @@ def _committed_query_source(committed_query: dict) -> str:
 # read like an error.
 _QUERY_DRIFT_STATUS_LABELS = {
     "direct_query_id_unverified": "Org-managed (pinned)",
-    "direct_query_id_optin_stale_risk": "Pinned — may predate an enabled feature",
+    "direct_query_id_optin_stale_risk": "Pinned — can't verify locally",
 }
 
 

{forward_netbox-2.4.2 → forward_netbox-2.4.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "forward-netbox"
-version = "2.4.2"
+version = "2.4.3"
 description = "NetBox plugin to sync Forward data into NetBox via built-in NQE queries"
 authors = ["Craig Johnson <craigjohnson@forwardnetworks.com>"]
 license = "MIT"