[BinoyOza-okta]

Fix ValidationError in list_network_zones() for Dynamic and Enhanced Dynamic zones

Summary

Fixes a Pydantic ValidationError raised by NetworkZoneApi.list_network_zones() and get_network_zone() when a response contains a DYNAMIC or DYNAMIC_V2 zone with asns or locations values. This includes the empty list [] the API returns for Enhanced Dynamic zones with no ASNs configured.

Problem

pydantic_core.ValidationError: 1 validation error for EnhancedDynamicNetworkZoneAllOfAsnsInclude
  Input should be a valid dictionary or instance of EnhancedDynamicNetworkZoneAllOfAsnsInclude
  [type=model_type, input_value=[], input_type=list]

Because a single bad zone fails deserialization, the whole paginated list call fails.

Root cause

openapi/api.yaml declared these fields by wrapping an array schema in allOf:

include:
  allOf:
    - $ref: '#/components/schemas/NetworkZoneAsns'   # type: array
    - description: An array of ASNs to include ...

OpenAPI Generator 7.7.0 treats this wrapper as a new object type, so it generated empty models with no fields instead of List[...]. Pydantic correctly rejects a list for an object type. This isn't caused by Pydantic v2 strictness or by empty lists: populated lists fail too, and the empty models would drop the data anyway.

The pattern appeared in 6 places:

Model	Field	Before	After
DynamicNetworkZone	asns	DynamicNetworkZoneAllOfAsns	List[StrictStr] (max 75)
DynamicNetworkZone	locations	DynamicNetworkZoneAllOfLocations	List[NetworkZoneLocation] (max 75)
EnhancedDynamicNetworkZoneAllOfAsns	include / exclude	...AsnsInclude / ...AsnsExclude	List[StrictStr] (max 75)
EnhancedDynamicNetworkZoneAllOfLocations	include / exclude	...LocationsInclude / ...LocationsExclude	List[NetworkZoneLocation] (max 75)

IP zones (gateways / proxies) are not affected.

Changes

• openapi/api.yaml, aligned with the merged upstream spec:
  • Replaced the 6 allOf wrappers with inline array definitions. Descriptions are kept.
  • Each array declares maxItems: 75, and the location arrays keep nullable: true.
  • ipServiceCategories.include / exclude now use maxItems: 75 instead of the previous maximum: 75, which has no effect on arrays.
  • Removed the now-unused NetworkZoneAsns and NetworkZoneLocationArray components.
• Regenerated:
  • Models: dynamic_network_zone.py, enhanced_dynamic_network_zone_all_of_asns.py, enhanced_dynamic_network_zone_all_of_locations.py and enhanced_dynamic_network_zone_all_of_ip_service_categories.py.
  • Their docs, and the lazy import maps in okta/__init__.py and okta/models/__init__.py.
• Removed: the 6 obsolete wrapper models, their docs, and their links in okta/DOC_GUIDE.md.
• Tests: added tests/test_network_zone_arrays.py.

Breaking change note

• Removed classes: DynamicNetworkZoneAllOfAsns, DynamicNetworkZoneAllOfLocations and EnhancedDynamicNetworkZoneAllOf{Asns,Locations}{Include,Exclude}. They had no fields and could never hold data, so no working code could have depended on them. Code that imports them by name should use plain lists instead: List[str]for ASNs andList[NetworkZoneLocation]` for locations.
• New 75-entry limit: asns, locations and ipServiceCategories lists with more than 75 entries now raise ValidationError when parsing a response, building a request model, or assigning to the field. This follows the maxItems: 75 declared in the upstream spec.

Testing

• tests/test_network_zone_arrays.py: 77 tests covering:
  • empty, populated and null payloads
  • discrimination through NetworkZone.from_dict
  • to_dict / JSON round trips, _links and proxyType validation
  • the 75-entry limit on all 8 arrays (75 accepted, 76 rejected on parse and on assignment)
  • regression guards for the removed models
• Coverage of the 5 network zone models is 98%. The 5 uncovered lines are generator else branches for dict-valued nested fields, which can't be reached with Pydantic v2 validation on.
• Existing unit tests (323) and the network zone integration tests (3) pass.

[dhiwakar-okta]

LGTM 🚀

[dhiwakar-okta]

LGTM 🚀