Current Series Release Notes

6.4.0-17

New Features

  • Adds --status and --zone-id filter options to the zone export list command.

  • Adds --status, --zone-id, and --message filter options to the zone import list command.

  • Adds --status filter option to the zone transfer accept list command.

  • Adds a --status filter option to the zone transfer request list command, allowing users to filter zone transfer requests by status.

  • Zone task list methods (zone_transfers.list_requests(), zone_transfers.list_accepts(), zone_exports.list(), and zone_imports.list()) now support pagination parameters (criterion, marker, limit), matching the pattern used by other v2 controllers.

  • CLI list commands for zone exports, zone imports, and zone transfer accepts now automatically paginate through all results using get_all().

  • Adds a dns limit list CLI command to display the DNS service limits (GET /limits).

  • Added --attributes option to openstack zone import create command. This allows users to pass zone attributes (e.g. pool_id) when importing a zonefile, using the same key:value format as openstack zone create. When attributes are provided, the client sends the request as application/json instead of text/dns. Existing behavior without --attributes is unchanged.

  • Adds a zone nameservers list CLI command to list the nameservers assigned to a zone (GET /zones/{zone_id}/nameservers).

Upgrade Notes

  • zone_exports.list() and zone_imports.list() now return a list of items directly instead of the raw API response dict. Code that previously accessed result["exports"] or result["imports"] should use the return value directly. This aligns these methods with all other v2 list controllers which already use response_key.

Bug Fixes

  • Wires up the existing --pattern filter option in the dns blacklist list command so it is actually passed to the API.

  • Wires up the existing --name filter option in the tld list command so it is actually passed to the API. Removes the --description filter which is not supported by the API.

  • “–email” is no longer an effectively required argument when creating zone. It is now only required for PRIMARY zone type, and is silently ignored for SECONDARY zone type.