netbox-interface-name-rules 1.4.0__tar.gz → 1.4.2__tar.gz

{netbox_interface_name_rules-1.4.0 → netbox_interface_name_rules-1.4.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: netbox-interface-name-rules
-Version: 1.4.0
+Version: 1.4.2
 Summary: NetBox plugin for automatic interface renaming when modules are installed
 Author: Marcin Zieba
 License-Expression: Apache-2.0
@@ -93,7 +93,7 @@ See the [full configuration guide](https://marcinpsk.github.io/netbox-InterfaceN
 
 ## Compatibility
 
-- NetBox ≥ 4.2.0
+- NetBox ≥ 4.3.0 (CI tests 4.3, 4.5, 4.6)
 - Python ≥ 3.12
 
 ## License
@@ -110,3 +110,30 @@ Apache 2.0
 See [CONTRIBUTING.md](CONTRIBUTING.md) for how to submit code or interface name rules.
 
 Community-contributed rules for various vendors are in the [`contrib/`](contrib/) directory.
+
+## Testing
+
+Inside the devcontainer:
+
+```bash
+netbox-test                 # run this plugin's tests (shared test_netbox DB)
+netbox-test-isolated <app> [flags]   # run on a per-session ISOLATED test DB
+```
+
+`netbox-test-isolated` is concurrency-safe: Django otherwise names the test
+database `test_<DB_NAME>` (`test_netbox`), so two `manage.py test` runs in the
+same devcontainer collide on one DB and corrupt each other's migrations (a
+crashed run can even leave an `idle in transaction` connection holding locks that
+wedges every later run). The helper points the test DB at a unique name —
+derived from the first app argument, or `TEST_DB_NAME=...` — via the
+[`isolated_test_settings`](.devcontainer/config/isolated_test_settings.py) shim
+(`--settings=isolated_test_settings` with `.devcontainer/config` on `PYTHONPATH`).
+Plain `netbox-test` keeps using the shared default (`test_netbox`);
+`netbox-test-isolated` instead derives a per-app DB name by default — `test_<app>`
+from the first app argument (this plugin when none is given) — unless you set
+`TEST_DB_NAME` explicitly. Example — test a sibling plugin without disturbing a
+parallel run:
+
+```bash
+netbox-test-isolated netbox_nso_plugin --keepdb
+```

{netbox_interface_name_rules-1.4.0 → netbox_interface_name_rules-1.4.2}/README.md

@@ -70,7 +70,7 @@ See the [full configuration guide](https://marcinpsk.github.io/netbox-InterfaceN
 
 ## Compatibility
 
-- NetBox ≥ 4.2.0
+- NetBox ≥ 4.3.0 (CI tests 4.3, 4.5, 4.6)
 - Python ≥ 3.12
 
 ## License
@@ -87,3 +87,30 @@ Apache 2.0
 See [CONTRIBUTING.md](CONTRIBUTING.md) for how to submit code or interface name rules.
 
 Community-contributed rules for various vendors are in the [`contrib/`](contrib/) directory.
+
+## Testing
+
+Inside the devcontainer:
+
+```bash
+netbox-test                 # run this plugin's tests (shared test_netbox DB)
+netbox-test-isolated <app> [flags]   # run on a per-session ISOLATED test DB
+```
+
+`netbox-test-isolated` is concurrency-safe: Django otherwise names the test
+database `test_<DB_NAME>` (`test_netbox`), so two `manage.py test` runs in the
+same devcontainer collide on one DB and corrupt each other's migrations (a
+crashed run can even leave an `idle in transaction` connection holding locks that
+wedges every later run). The helper points the test DB at a unique name —
+derived from the first app argument, or `TEST_DB_NAME=...` — via the
+[`isolated_test_settings`](.devcontainer/config/isolated_test_settings.py) shim
+(`--settings=isolated_test_settings` with `.devcontainer/config` on `PYTHONPATH`).
+Plain `netbox-test` keeps using the shared default (`test_netbox`);
+`netbox-test-isolated` instead derives a per-app DB name by default — `test_<app>`
+from the first app argument (this plugin when none is given) — unless you set
+`TEST_DB_NAME` explicitly. Example — test a sibling plugin without disturbing a
+parallel run:
+
+```bash
+netbox-test-isolated netbox_nso_plugin --keepdb
+```

{netbox_interface_name_rules-1.4.0 → netbox_interface_name_rules-1.4.2}/netbox_interface_name_rules/__init__.py

@@ -2,7 +2,7 @@
 # Copyright (C) 2025 Marcin Zieba <marcinpsk@gmail.com>
 from netbox.plugins import PluginConfig
 
-__version__ = "1.4.0"
+__version__ = "1.4.2"
 
 
 class InterfaceNameRulesConfig(PluginConfig):