netbox-windows-dhcp-plugin 0.1.0__tar.gz

netbox_windows_dhcp_plugin-0.1.0/.gitignore

@@ -0,0 +1,25 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+build/
+dist/
+.pytest_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+site/
+dev/data/
+.env
+
+# Local Claude Code notes, kept out of the repo
+CLAUDE.md
+.claude/
+
+# Lab server settings and credentials for the dev stack
+dev/env/lab.env
+# Lab test output (raw envelopes and property dumps): may identify the lab, never commit
+.lab/
+
+# Browser automation scratch output
+.playwright-mcp/

netbox_windows_dhcp_plugin-0.1.0/CHANGELOG.md

@@ -0,0 +1,247 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project uses [Semantic Versioning](https://semver.org/).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-10-27
+
+Release candidates 0.1.0rc1 to 0.1.0rc5 (2026-10-21 to 2026-10-23) went to PyPI for testing; what testing them found
+is listed under Fixed.
+
+First release. Every v1 feature is in place and tested against the fake server and PowerShell stubs. The lab tests
+against real Windows servers (`make test-lab`, `make lab-e2e`) ran in full on two Windows Server 2022 DHCP servers,
+failover included; what they found is listed under Fixed, and the few details they could not reach are listed in
+the documentation's limitations page.
+
+### Added
+
+Connections and security
+
+- Windows server connection settings linked to netbox-plugin-dhcp servers: WinRM (NTLM, Basic, Kerberos or CredSSP, HTTPS by
+  default; CredSSP is what failover writes need) or SSH, with an optional `computer_name` for a management host.
+- Credential profiles in `PLUGINS_CONFIG`, each secret inline, from an environment variable or a file. Nothing secret
+  is stored in the database, the change log or job logs.
+- `allowed_hosts` on credential profiles limits which hosts their credentials can be sent to, checked when a Windows
+  server is saved and before every connection. Basic authentication requires HTTPS with certificate checks. SSH
+  always verifies the host key (pinned key or the worker's known_hosts).
+- "Test connection" button and REST action, run as a background job.
+
+Models and API
+
+- Models for what netbox-plugin-dhcp does not hold: Windows scope and reservation settings (including the DHCPv6
+  IAID), exclusion ranges, user and vendor classes, option definitions (Windows data type and default value),
+  option qualifiers, vendor class option definitions and values, policies, failover relationships, MAC filters and
+  the allow and deny list switches.
+- Sync bookkeeping: sync state, sync runs and import proposals.
+- REST API and GraphQL for every model. Names of classes, policies, superscopes and failover relationships compare
+  without case, as on Windows.
+
+Import (Windows to NetBox)
+
+- IPv4 scopes, superscopes, exclusion ranges, reservations, user and vendor classes, option definitions, vendor class
+  options, policies (conditions, IP ranges, processing order, lease time), failover relationships, MAC filters and
+  option values at server, scope, reservation, user class and policy level. They become netbox-plugin-dhcp objects
+  plus the prefixes, IP ranges, IP addresses and MAC addresses they need, in the server's import VRF. Objects missing
+  on Windows are proposed for deletion.
+- DHCPv6 scopes (lifetimes, T1 and T2, state, preference), reservations (DUID, IAID), user classes and option values
+  against netbox-plugin-dhcp's standard DHCPv6 definitions. DHCPv6 vendor classes and values, other option codes and
+  exclusion ranges are noted and left alone.
+- Option values containing a comma, stored as `\,` (Kea's escape).
+- With netbox-branching, the **Import** button is a menu: **Import into branch** (an import branch, the default),
+  **Import into this branch** (the branch you work in, no new branch) and **Import directly** (into main, after a
+  confirmation page, with your permissions checked object by object and change control's `protect_main` respected;
+  the new `import_direct` setting turns it off). The REST import action takes the same choice as `destination`. Sync
+  runs record where each import wrote (new **Destination** column and filter), and the Import panel says so while
+  the import is queued, running and done (#36).
+- With netbox-branching, each import writes into a branch `dhcp-import/<server>/<timestamp>` (reused while open) and,
+  with netbox-change-control, opens a change request submitted for review.
+- Without branching, each import fills an import proposal whose items are applied or dismissed one by one, in bulk
+  or for the whole proposal, from the UI or the REST API. Applying writes as the reviewing user, checks their
+  permissions, and refuses items whose NetBox object changed since the import.
+- "Import now" button and REST action, and scheduled imports every `import_interval` minutes (`import_user` for
+  scheduled imports with branching).
+
+Push (NetBox to Windows)
+
+- A reconcile per server that creates, updates and deletes every kind above, in dependency order, so Windows matches
+  NetBox.
+- Only objects recorded in sync state are deleted. Objects created by hand on Windows are left alone, and so are
+  managed objects changed on Windows since the last push and objects whose removal would take unmanaged ones with
+  them. Identical objects are adopted as managed; applying an import item adopts it straight away.
+- NetBox data Windows cannot hold (a scope without a pool, a reservation without a MAC address, options 1 and 51,
+  values of codes Windows does not define) is reported in the sync run instead of pushed. A scope subnet mask or an
+  option definition type is never changed in place, and a scope with leases is never force-removed.
+- With netbox-branching, merging or reverting a branch queues a push for each Windows server it touched. Other saves
+  (all of them without branching, direct edits of main with it) queue one push per server after commit,
+  `push_debounce` seconds later. `sync_enabled = False` stops pushes.
+- "Sync now" and "Dry run" buttons and REST actions. A dry run records the planned changes in its sync run.
+- Failover: relationships are written on the primary, with the shared secret read from the credential profile named
+  in `shared_secret_profile`; the changed scopes are then replicated to the partner. A scope leaving a relationship
+  leaves it before it is deleted, and a scope with leases is refused before anything changes.
+- One import or push per server at a time across all workers (a PostgreSQL advisory lock); a busy push retries a
+  minute later.
+
+Leases
+
+- A Leases tab on the subnet page of Windows scopes (IPv4 and DHCPv6) reads the live leases in a background job.
+  Viewing needs the subnet and its Windows server, loading needs permission to change the server, and is refused
+  inside a branch. Leases are not stored.
+
+Documentation
+
+- A documentation site (https://thomaschristory.github.io/netbox-windows-dhcp-plugin/): installation, preparing
+  Windows, configuration, a first-sync walkthrough, how objects map, import, push, DHCPv6, failover, leases,
+  permissions, REST API and GraphQL, security, workers and jobs, troubleshooting and limitations.
+- Screenshots from a lab run on real Windows servers: the first-sync walkthrough step by step, import proposals and
+  import branches with change requests, a new scope built in NetBox and pushed, a failover relationship, the Leases
+  tab and a failed push.
+- Installation: netbox-change-control needs at least one policy, or change requests (an import's included) can never be
+  approved. How objects map: netbox-plugin-dhcp 0.2.0 does not save comments from its edit forms
+  (sys4/netbox-plugin-dhcp#68).
+- `SECURITY.md`: report vulnerabilities through GitHub's private vulnerability reporting.
+
+Development
+
+- `dev/scripts/lab-server-setup.ps1` prepares a Windows Server VM as the lab server (DHCP role, a least-privilege
+  account, WinRM over HTTPS).
+- Opt-in lab tests against a real Windows DHCP server: `make test-lab` (the client over WinRM, one round trip per
+  unverified cmdlet) and `make lab-e2e` (import, push and leases on the dev stack). They only touch `nbwd-test-`
+  objects in `198.18.0.0/15` and `2001:db8:4e42::/64`.
+
+### Fixed
+
+- The Windows servers list links each server's name to its Windows server page (actions, Import panel, sync runs),
+  as the sync run pages do, saved table layouts included; the generic netbox-plugin-dhcp server stays linked in a
+  new **Generic DHCP server** column (#38).
+- The plugin's buttons (Test connection, Sync now, Dry run, Import now, and Apply all, Dismiss all, Apply and Dismiss
+  on the review queue) were rendered without a CSRF token, so clicking them failed with "CSRF verification failed"
+  (403). They now carry the token (#19).
+- Read-only pages (sync runs, import proposals and their items) showed Edit, Clone, Add, Import or Edit Selected
+  buttons that led to a "None" address and a 404. Pages now show only the buttons whose views exist; Delete and the
+  review actions stay. Lists without CSV import or bulk edit no longer offer those buttons either (#23).
+
+Found by a first, partial lab run against Windows Server 2025:
+
+- A Windows object that does not exist is reported as missing again, instead of as an object with every field empty.
+  Windows PowerShell 5.1 printed "nothing found" as `{}`; the script envelope now turns it into `null`, and the
+  client also reads `{}` as missing. This affected MAC filters, superscopes, policies, DHCPv6 scopes, classes,
+  option values and every other lookup (#15).
+- Renaming a superscope uses the cmdlet's real `-Name` parameter instead of `-SuperscopeName`, which Windows rejected
+  (#14).
+- Option values on an IPv4 reservation are written and removed with `-ReservedIP` alone: Windows refuses `-ScopeId`
+  next to it, so a push of a reservation option failed (#20).
+- Option values on a DHCPv6 reservation are written and removed with `-ReservedIP` alone, for the same reason with
+  `-Prefix` (#17).
+- DHCPv6 leases no longer read an `AddressState` property Windows does not have; the Leases tab shows their state as
+  n/a, since Windows reports none for DHCPv6 (#22).
+- The policy lab test uses a condition Windows accepts (`*.Example.Test`), checks FQDN policies apart from policy IP
+  ranges and option values (which Windows refuses on FQDN policies, DHCP 20135 and 20136), and the fake server now
+  refuses a wildcard in the middle of a condition, as Windows does (#18).
+- A new DHCPv6 scope pushed without renewal and rebinding times now gets Windows' own default rebinding time (T2),
+  6.4 days (6 days 9:36), instead of 6 days 10 hours, so it matches a scope made on Windows without them (#16).
+  Renewal and rebinding times left empty in NetBox now follow the scope's preferred lifetime (half and 80 % of it,
+  which gives Windows' 4 and 6.4 days for the default 8 days), so a scope with a preferred lifetime shorter than
+  6.4 days no longer gets timers past it, which Windows documents as invalid. An existing scope keeps its Windows
+  timers while they still fit below the preferred lifetime. When only one of T1 and T2 is set in NetBox, the empty
+  one is now worked out against it (T1 at 5/8 of T2, or T2 halfway between T1 and the preferred lifetime, when the
+  default would not fit), instead of a default that could land on the wrong side and be refused by Windows.
+- Policy conditions Windows stores in its own spelling no longer show as changed after every push or import: a MAC
+  prefix such as `02-4e-42-ab*` (read back as `02-4e-42-ab-*`) and a host name in mixed case (read back in
+  lowercase) now compare equal, so a second push is a no-op (#21). Upgrading from 0.1.0rc1: a policy whose condition
+  NetBox spells differently from Windows was recorded under its old spelling, so until the next push records it
+  again, deleting it in NetBox is reported as changed on Windows and not deleted. Push once after upgrading.
+- A push now creates and updates the policies of each level in ascending processing order instead of by name, so
+  recreating policies whose names sort the other way no longer fails with DHCP 20110. Policies Windows moves down
+  when another takes their number are set back in the same push, and a processing order that would leave a gap is
+  reported in the plan instead of failing on Windows (#24). After a policy is deleted in NetBox without renumbering
+  the ones after it, the push no longer moves the others into the wrong order: it leaves that level as Windows holds
+  it and asks for the renumbering. Policies Windows renumbers by itself (after a delete, for example) are no longer taken for
+  policies changed on Windows when NetBox later deletes them: the processing order is no longer part of what the
+  push compares to notice hand edits.
+
+Found by testing 0.1.0rc2:
+- The Windows server page has an **Import** panel saying whether the latest import is queued, running or finished
+  and where it went. With branching it names and links the import branch and its change request and says main has
+  not changed; without branching it links the import proposal and does not mention branches. It refreshes itself
+  while the job runs, and the sync run page shows the same for its own run. The message after **Import now** also
+  says where the import will go (#32).
+- Changing a scope's pool so that one end grows and the other shrinks (for example `.10-.200` to `.11-.210`) no
+  longer fails with DHCP 20023, which Windows returns for that change in one call. The push changes the range in
+  two steps: it first narrows to the addresses both pools share (or, when they do not overlap, widens over both),
+  then sets the final range. If the second step fails, it tries to put the old range back (#30).
+- Updating a hot standby failover relationship no longer fails with "A parameter cannot be found that matches
+  parameter name 'ServerRole'": `Set-DhcpServerv4Failover` has no such parameter, so the push no longer sends it.
+  Windows cannot change the role (active or standby) in place, so a push that changes it is refused with a message
+  saying to recreate the relationship. After switching a relationship to hot standby, the push checks the role
+  Windows chose against NetBox. Mode changes no longer wait for a confirmation nobody can answer (#33).
+- The policy lab test allows the lease time option (51) Windows lists next to a policy's own option values (#29).
+- The missing-module unit test no longer fails on a host with the Windows DHCP management tools (RSAT) installed: it
+  runs PowerShell with an empty module path (#31).
+
+Found by testing 0.1.0rc3:
+- A reservation description or name change no longer drops its option values on Windows (IPv4 and DHCPv6, #42).
+  The push only sends the client ID, type, DUID or IAID when they change, and puts back any reservation option value
+  Windows removed during the update. The dry run is unchanged: it still lists only the reservation update. If a value
+  cannot be put back, the reservation change is reported as failed, naming each lost option and saying whether it
+  comes back by itself: the next push recreates a value NetBox holds, but values NetBox does not hold (DHCPv6 vendor
+  class values, option codes the plugin does not sync, values added on Windows since the last import) must be put
+  back by hand.
+- Without branching, an import that finds only differences a reviewer already dismissed no longer reports "No
+  differences found." The Import panel and the sync run now say that nothing new waits for review and how many
+  dismissed differences stay ignored while Windows shows the same values. The count of differences waiting for review
+  no longer includes dismissed ones, a proposal you may not view is no longer read as "no differences", and the sync
+  run summary and job log record how many differences were dismissed earlier (#43). An earlier run whose proposal a
+  later import took over (or that was deleted) says so and links the server's open proposal instead of claiming a
+  proposal you may not view, and a run recorded before this fix with no proposal linked says only how many
+  differences it found.
+- The Windows scopes list shows each scope's prefix in its own column, next to the subnet name, as the
+  netbox-plugin-dhcp subnet list does, so scopes with similar or repeated names are told apart without opening them.
+  The column links to the prefix and sorts by network (#47).
+- With branching, the Import panel no longer calls a merged or deleted branch "the open import branch", on the
+  Windows server page or on the sync run of an earlier import. It says what became of the branch: being merged,
+  merged into main (with the time), merged and since deleted, or deleted without being merged, read from the branch
+  or from its deletion in the change log. With no record you may view, it says the outcome is not known rather than
+  guessing a merge. A merged import no longer reads as "main matches Windows", the deleted branch row links its
+  deletion record, and the server panel links the server's import history (#44).
+
+Found by testing 0.1.0rc4:
+- Failover replication after a push to the primary no longer fails with `AmbiguousParameterSet`. The plugin passed
+  both `-Name` and `-ScopeId` to `Invoke-DhcpServerv4FailoverReplication`, which takes one or the other; it now
+  replicates the changed scopes with `-ScopeId` only, never widening the copy to the whole relationship (#51).
+- A failed failover replication is retried by the next push to the primary, even one with nothing else to write, so
+  the partner no longer stays behind until the next change. The push's sync run lists the scopes still to replicate.
+  A scope that is not yet in the relationship on Windows waits for a later push instead of blocking the others.
+
+Found by the full lab run (two Windows Server 2022 servers; earlier notes said 2025, which is what the rc testers
+ran):
+- Over SSH, about one PowerShell run in fifteen hung until the timeout: Windows OpenSSH sometimes loses the end of
+  stdin, and the script loader read stdin to its end. It now reads the one line the script is sent as. Each hung
+  run also kept its SSH session open, so after a few the server refused new ones (#56). Windows OpenSSH also stalls
+  on more than about 70 KB of input: the SSH transport refuses a script above 64 KB at once, saying to use WinRM, and
+  a run that stays silent past the command timeout now says so instead of giving an empty error.
+- Failover relationships could not be created over WinRM: `Add-DhcpServerv4Failover` asked for a confirmation nobody
+  can answer ("PowerShell is in NonInteractive mode"). Add, Set and replication now send `-Force`. The removes never
+  do: they do not ask while the relationship is healthy, and with the partner unreachable `-Force` would remove the
+  relationship or scope on one server only. Such a push now fails with "not in NORMAL state" and changes nothing.
+- Failover writes need the DHCP server to reach its partner as you, which NTLM and Kerberos cannot pass on
+  (`PermissionDenied`). The new **CredSSP** WinRM authentication makes them work; see the failover page. CredSSP
+  hands the password to the server, so it requires HTTPS with certificate verification, unless the credential
+  profile sets `allow_insecure_credssp` (for labs).
+- An import or push no longer fails when a scope disappears while the server is being read (for example the partner's
+  copy, when a failover relationship is removed at that moment): that scope counts as gone, the rest is read. The
+  sync run's notes and the job log name each scope left out this way (#58).
+- A failover relationship imported with message authentication on made every later push to that server fail: the
+  import cannot read the secret, so NetBox had no shared secret profile and each push tried to turn authentication
+  off, which Windows refuses. Without a profile NetBox now leaves authentication as Windows has it; a profile still
+  turns it on with that secret. Found while taking the documentation screenshots.
+- A sync run's page listed every import proposal of every server instead of its own (the filter it used did not
+  exist).
+- The Kerberos SPN help text read "Defaults to WSMAN/": the host placeholder was dropped as an HTML tag.
+- A failover partner Windows names by its computer name now matches a server NetBox knows by IP address, and one it
+  names by address matches a server NetBox knows by name (#57). Windows names the partner by its computer name on one
+  side of a relationship, so that side's import failed and its pushes saw a partner change Windows cannot make. Test
+  connection, imports and pushes now record the DHCP server's computer name, DNS name and addresses (**Reported
+  names**, migration 0006, cleared when the host or computer name changes), and partners match on them as well as on
+  the host. A name two servers report matches neither, and the error says so.

netbox_windows_dhcp_plugin-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

netbox_windows_dhcp_plugin-0.1.0/PKG-INFO

@@ -0,0 +1,137 @@
+Metadata-Version: 2.5
+Name: netbox-windows-dhcp-plugin
+Version: 0.1.0
+Summary: Sync netbox-plugin-dhcp data with Microsoft Windows DHCP servers over WinRM or SSH.
+Project-URL: Homepage, https://github.com/thomaschristory/netbox-windows-dhcp-plugin
+Project-URL: Documentation, https://thomaschristory.github.io/netbox-windows-dhcp-plugin/
+Project-URL: Repository, https://github.com/thomaschristory/netbox-windows-dhcp-plugin
+Project-URL: Changelog, https://github.com/thomaschristory/netbox-windows-dhcp-plugin/blob/main/CHANGELOG.md
+Project-URL: Issues, https://github.com/thomaschristory/netbox-windows-dhcp-plugin/issues
+Author: Thomas Christory
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: ddi,dhcp,netbox,netbox-plugin,windows,winrm
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Framework :: Django
+Classifier: Intended Audience :: System Administrators
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: System :: Networking
+Requires-Python: >=3.12
+Requires-Dist: netbox-plugin-dhcp<0.3,>=0.2
+Requires-Dist: paramiko>=3.5
+Requires-Dist: pypsrp[credssp]>=0.8
+Provides-Extra: branching
+Requires-Dist: netbox-change-control>=0.6; extra == 'branching'
+Requires-Dist: netboxlabs-netbox-branching>=1.2.2; extra == 'branching'
+Provides-Extra: kerberos
+Requires-Dist: pypsrp[kerberos]>=0.8; extra == 'kerberos'
+Description-Content-Type: text/markdown
+
+# netbox-windows-dhcp-plugin
+
+A NetBox plugin that keeps Microsoft Windows DHCP servers in step with the data modelled by
+[netbox-plugin-dhcp](https://github.com/sys4/netbox-plugin-dhcp), in both directions, over WinRM or SSH.
+
+**Documentation: https://thomaschristory.github.io/netbox-windows-dhcp-plugin/**
+
+> **Status: 0.1.0, the first release.** Every v1 feature is built and tested against an in-memory fake server and
+> PowerShell stubs, and the lab tests have run in full against two Windows Server 2022 DHCP servers (import, push,
+> leases and failover, over WinRM HTTP and HTTPS and over SSH). Kerberos and SSH key authentication have not been
+> tried on a real server yet (see the
+> [limitations](https://thomaschristory.github.io/netbox-windows-dhcp-plugin/limitations/)). Try it on a lab server
+> first.
+
+## Features
+
+- **Import** from Windows, on demand or every `import_interval` minutes. With
+  [netbox-branching](https://github.com/netboxlabs/netbox-branching) each import lands in a branch (plus a change
+  request with [netbox-change-control](https://github.com/antoinekh/netbox-change-control)); without it, in an import
+  proposal whose items you apply or dismiss.
+- **Push** to Windows: a reconcile per server when a branch is merged, or a few seconds after a save without
+  branching, plus "Sync now" and "Dry run". A push only deletes Windows objects NetBox manages; objects made by hand
+  on Windows are left alone until imported.
+- IPv4 scopes, superscopes, exclusion ranges, reservations, option definitions and values, user and vendor classes,
+  vendor class options, policies, failover relationships (with replication to the partner) and MAC filters.
+- DHCPv6 scopes, reservations (DUID and IAID), user classes and option values.
+- A **Leases** tab on the subnet page, read live from Windows in a background job.
+- WinRM (NTLM, Kerberos, Basic, CredSSP for failover; HTTPS by default) or SSH, as in
+  [terraform-provider-windowsddi](https://github.com/thomaschristory/terraform-provider-windowsddi). Credentials
+  live in named profiles in the plugin configuration, limited to `allowed_hosts`, never in the database.
+- REST API and GraphQL for every model; all Windows I/O in background jobs.
+
+## Compatibility
+
+| Plugin | NetBox | netbox-plugin-dhcp | netbox-branching | Python |
+|---|---|---|---|---|
+| 0.1.x | 4.7 | 0.2.x | 1.2.2+ (optional) | 3.12 to 3.14 |
+
+Windows Server 2016 or later with the DHCP Server role.
+
+## Quick start
+
+```bash
+pip install netbox-windows-dhcp-plugin
+# extras: [kerberos] for Kerberos (needs system GSSAPI libraries), [branching] for branching and change control
+```
+
+```python
+PLUGINS = ["netbox_dhcp", "netbox_windows_dhcp_plugin"]
+
+PLUGINS_CONFIG = {
+    "netbox_windows_dhcp_plugin": {
+        "credentials": {
+            "dhcp-admin": {
+                "username": "CORP\\svc-netbox-dhcp",
+                "password_env": "DHCP_ADMIN_PASSWORD",
+                "allowed_hosts": ["dhcp*.corp.example"],
+            },
+        },
+    },
+}
+```
+
+Run `python manage.py migrate`, restart NetBox and its worker, then add a Windows server under **Windows DHCP >
+Windows servers**, click **Test connection** and **Import now** (**Import** with netbox-branching). The
+[first sync](https://thomaschristory.github.io/netbox-windows-dhcp-plugin/quickstart/) walkthrough covers the rest.
+
+## Documentation
+
+- [Installation](https://thomaschristory.github.io/netbox-windows-dhcp-plugin/installation/) and
+  [preparing Windows](https://thomaschristory.github.io/netbox-windows-dhcp-plugin/windows-setup/)
+- [Configuration](https://thomaschristory.github.io/netbox-windows-dhcp-plugin/configuration/) and
+  [security](https://thomaschristory.github.io/netbox-windows-dhcp-plugin/security/)
+- [How objects map](https://thomaschristory.github.io/netbox-windows-dhcp-plugin/mapping/),
+  [import](https://thomaschristory.github.io/netbox-windows-dhcp-plugin/import/) and
+  [push](https://thomaschristory.github.io/netbox-windows-dhcp-plugin/push/)
+- [Permissions](https://thomaschristory.github.io/netbox-windows-dhcp-plugin/permissions/),
+  [REST API and GraphQL](https://thomaschristory.github.io/netbox-windows-dhcp-plugin/api/),
+  [troubleshooting](https://thomaschristory.github.io/netbox-windows-dhcp-plugin/troubleshooting/)
+- [Design](https://github.com/thomaschristory/netbox-windows-dhcp-plugin/blob/main/docs/DESIGN.md) and
+  [changelog](https://github.com/thomaschristory/netbox-windows-dhcp-plugin/blob/main/CHANGELOG.md)
+
+The same pages are in the [`docs/`](https://github.com/thomaschristory/netbox-windows-dhcp-plugin/tree/main/docs)
+folder of the repository.
+
+## Development
+
+Requires [uv](https://docs.astral.sh/uv/) and Docker.
+
+```bash
+make lint        # ruff check and format check
+make test        # unit tests, no NetBox needed
+make dev         # NetBox, netbox-plugin-dhcp, branching and change control in docker
+make test-netbox # NetBox integration tests inside the dev stack
+make docs        # build the documentation site
+make dist        # build and check the wheel and sdist
+```
+
+See [Development](https://thomaschristory.github.io/netbox-windows-dhcp-plugin/development/) for the lab tests
+against a real Windows server.
+
+## License
+
+Apache-2.0, see [LICENSE](https://github.com/thomaschristory/netbox-windows-dhcp-plugin/blob/main/LICENSE).