Changes in Release 26.05

New Functionality 

Minor improvements

FortiOS:

Generate API token during initial device configuration
Streamline and speed up the initial device configuration (which could be a breaking change if you use an old FortiOS version without a license).

Arista EOS:

We made major changes to the fortinet initial device configuration playbook:

The playbook generates an API token for the netlab user (which should have been added during the Vagrant box creation process). Set netlab_generate_api_token node/group variable to False to disable this step.
The configuration deployment process uses HTTPS instead of HTTP (which just redirects to HTTPS in most cases). This might not work if you’re using a Fortinet device without a license. Set the following node/group variables to use HTTP:

ansible_httpapi_use_ssl: false
ansible_httpapi_port: 80

The playbook tries to reach the FortiOS HTTPS server immediately after switching to multi-VDOM mode and will retry several times. When needed, use these node/group variables to increase the wait time.

Other breaking changes:

The ‘reload device configuration’ functionality relied on initial.reload: False feature flag to detect devices that do not support it. We added an explicit initial.reload feature to all devices, and changed the default behavior to “device does not support configuration reloads”. This might prevent configuration reloads from working on custom devices.