Changelog.md

@@ -2,12 +2,6 @@
 
 ## [Unreleased]
 
-## [0.2.2] - 07/05/2025
-
-### Fixed
-
-- Use `NB_CLUSTER_ID` even for VM update.
-
 ## [0.2.1] - 01/05/2025
 
 ### Fixed

README.md

@@ -27,9 +27,6 @@ The following env variables will need to be set:
 - **NB_API_URL**: The URL to your NetBox instance. (ex: https://netbox.example.org)
 - **NB_API_TOKEN**: The token created previously. (ex: f74cb99cf552b7005fd1a616b53efba2ce0c9656)
 
-You can also set the `NB_CLUSTER_ID` env variable in order to indicate the ID of the cluster that will be used in
-NetBox.
-
 You'll also need to perform a minimal configuration on NetBox:
 
 - Create the physical nodes hosting the cluster. (The name should match the one on Proxmox, so that the script can
@@ -63,5 +60,5 @@ The following env variables will need to be set:
 You can then execute the script using the following command:
 
 ```
-PVE_API_HOST=xx PVE_API_USER=xx PVE_API_TOKEN=xx PVE_API_SECRET=xx NB_API_URL=xx NB_API_TOKEN=xx nbpxsync
+PVE_API_HOST=xx PVE_API_USER=xx PVE_API_TOKEN=xx PVE_API_SECRET=xx NB_API_URL=xx NB_API_TOKEN=xx python3 -m netbox_pve_sync
 ```

netbox_pve_sync/__init__.py

@@ -143,7 +143,7 @@ def _process_pve_virtual_machine(
     else:
         nb_virtual_machine.name = _pve_virtual_machine['name']
         nb_virtual_machine.site = _nb_device.site.id
-        nb_virtual_machine.cluster = os.environ.get('NB_CLUSTER_ID', 1)
+        nb_virtual_machine.cluster = 1
         nb_virtual_machine.device = _nb_device.id
         nb_virtual_machine.vcpus = pve_virtual_machine_config['cores']
         nb_virtual_machine.memory = int(pve_virtual_machine_config['memory'])

pyproject.toml

@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "netbox-pve-sync"
-version = "0.2.2"
+version = "0.2.1"
 authors = [
     { name = "Aloïs Micard", email = "alois@micard.lu" },
 ]