fix(schema): leave number pool ranges unset in the write model when they are not declared

[polmichel]

Why

NumberPoolParametersWrite.ranges defaulted to an empty list, so a schema that leaves the ranges out of a NumberPool attribute's parameters dumped the same as one that declares ranges: []. The Infrahub server builds its internal schema from that dump, and could not tell "keep the stored ranges" from "remove every range".

Jira: IFC-3412

What changed

• In the write model, ranges is list[NumberPoolRangeWrite] | None and defaults to None. A schema that does not declare the ranges dumps without them; an explicit ranges: [] stays in the dump.
• The read model is unchanged.
• write.py is generated by invoke backend.generate in the Infrahub repository; the generator change and the submodule bump are in the companion Infrahub pull request.

Related to opsmill/infrahub#11089

How to review

Read the ranges field in infrahub_sdk/schema/generated/write.py, then the two tests in tests/unit/test_schema_offline_validation.py.

Tests

• test_number_pool_without_any_range_spelling_leaves_the_range_fields_absent now asserts that ranges is absent from the dump; it fails with the previous write model.
• New test_number_pool_explicit_empty_ranges_survive_the_dumps: an explicit ranges: [] stays in the server-side dump (exclude_none) and in SchemaRoot.to_schema_dict().

Tests against the live application

Run with this branch installed as the SDK of a local Infrahub stack running opsmill/infrahub#11089:

• client.schema.load with a NumberPool attribute declared with parameters: {}: the pool keeps its ranges. With ranges: []: the pool ends with zero ranges.
• Schema built with SchemaRoot.model_validate(...).to_schema_dict(): without ranges, parameters has no ranges key and the load keeps the ranges; with ranges=[], parameters is {"ranges": []} and the load removes them.
• infrahubctl schema load on a directory of two YAML files: parameters: {} keeps the ranges, ranges: [] removes them.

🤖 Generated with Claude Code

---

Summary by cubic

Makes the schema write model distinguish a NumberPool attribute that leaves its ranges undeclared from one that explicitly declares ranges: []. Previously both dumped the same empty list, so a schema reload could not tell "keep the stored ranges" from "remove every range" (IFC-3412). NumberPoolParametersWrite.ranges now defaults to None and is omitted from dumps when unset, while an explicit empty list is preserved.

^{Written for commit 8a04839. Summary will update on new commits.}

[cloudflare-workers-and-pages]

Deploying infrahub-sdk-python with    Cloudflare Pages

Latest commit:	8a04839
Status:	✅  Deploy successful!
Preview URL:	https://a6cd43e8.infrahub-sdk-python.pages.dev
Branch Preview URL:	https://pmi-number-pool-write-ranges.infrahub-sdk-python.pages.dev

View logs

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

@@                Coverage Diff                @@
##           infrahub-develop    #1424   +/-   ##
=================================================
  Coverage             86.86%   86.86%           
=================================================
  Files                   152      152           
  Lines                 14813    14813           
  Branches               1982     1982           
=================================================
  Hits                  12867    12867           
  Misses                 1382     1382           
  Partials                564      564           

Flag	Coverage Δ
integration-tests	42.38% <0.00%> (-0.08%)	⬇️
python-3.10	60.91% <0.00%> (-0.01%)	⬇️
python-3.11	60.92% <0.00%> (+<0.01%)	⬆️
python-3.12	60.92% <0.00%> (+<0.01%)	⬆️
python-3.13	60.92% <0.00%> (+0.02%)	⬆️
python-3.14	60.92% <0.00%> (+0.02%)	⬆️
python-filler-3.12	22.97% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
infrahub_sdk/schema/generated/write.py	99.40% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.