GAIA API version 2.0 is now GA !

[ameera]

Hi All,

I am happy to announce the release of GAIA API version 2.0 

GAIA API 2.0 significantly expands network configuration coverage, improves security posture, and increases API engine stability, making automation and orchestration of Gaia systems more complete and reliable.

This release is part of R82.20 GA, next jumbo releases, Offline SK.

Some of the new capabilities of the new version:

2New capabilities (all supported starting from Gaia R82.20)

• IPv6 routing: static routes (5 commands) and Policy Based Routing rules and tables (9).
• OSPFv3: 19 commands for show and set operations on instances, areas and interfaces, neighbors, the LSA database, stats, and more.
• Multicast: IPv4 and IPv6 Multicast Forwarding Cache show commands (10), static MFC entries (2), and static multicast routes (5).
• IPSec: set-ipsec, show-ipsec and show-all-ipsec. These configure AH/ESP with SPI, algorithms and keys.
• Secure Sync: show-secure-sync and set-secure-sync.

Updated APIs

• Routing:

• BGP peer-group management (add, set, delete, show-configuration).
• IGMP and MLD blocked groups, plus MLD SSM mapping.
• OSPFv2 show and set commands.
• PIM6 (set-ipv6-pim).

• Interfaces: VLAN, VXLAN, GRE, physical (including xcvr detail), bridge, bond and PPPoE.

I/S:

Security hardening:

• Fixed an unauthenticated remote code execution issue in Multi-Domain Server (SA-1164).
• Prevented argument injection in put-file, show-snmp-oid and add-license.
• Hardened session, task-status and task-monitor handling.

Functionality:

• Per-interface SGT enablement.
• 64-bit system support.
• IPv6 objects in license-add requests.
• OpenAPI 3.0 spec generation.
• Predictable JSON key ordering.
• Support for Marvell MHO systems.

Stability:

• Fixed gaia_api restart -f all leaving the API stopped.
• Fixed show-interfaces and show-password-policy.
• Fixed set-time-and-date.
• Fixed OpenTelemetry setup.
• Fixed run-script commands for non-local users.

Info:

•         Use this link to check the recent APIs documentation

•         Use this link to download the recent API engine and see the latest changelog

•          Use this link to update “API on demand” in Check-Mates

BR, Ameer

[Don_Paterson]

Great post. Thanks!

I just shared this feedback for the SK (to the SK team). 

Gaia API v2 (build 44) OpenAPI JSON: schema defects:

The OpenAPI collection published in sk143612 (FMW-8397) has generator faults that break code generation and validation:

1. Nested objects and arrays are typed as string (e.g. next-hop, dhcp, servers).
2. Internal type syntax leaks into enums (e.g. "all)", "int(1,65535").
3. Defaults are stored as strings (e.g. "false", "50").
4. components/schemas is empty, so no response models are defined.
5. Descriptions are wrong: show-vsnext-state says “Set”, show-virtual-switch says “Delete”.
6. Examples don’t match the schemas: show-maestro-site, show-isis-interface, show-mld-interface-ssm-map.
7. Error codes are documented wrongly in both places.

I tested on R82.20 JHFA Take 10, on an SMS and a VSNext gateway:
a bad SID returns 401, and missing fields, unknown objects and duplicates all return 400, distinguished only by the body’s code (err_validation_failed, object_not_found, object_already_exist). The spec lists 403/404/409 and never 401. sk143612 says failures return 500.

Could the generator be corrected so the spec is usable with standard OpenAPI tooling?