Releases: f5devcentral/f5-journeys
Releases · f5devcentral/f5-journeys
Release 4.2.0
Full config migration:
- Add support for selecting F5OS version for online mode
- Add support for STP configuration conflicts
Release 4.1.0
Full config migration:
- Add support for selecting F5OS version for offline mode
Per-app migration:
- Update f5-automation-config-converter container to version 1.23.3
4.0.0
Full Migration Journey:
- Add support for BIG-IP TMOS v17.1 running on VELOS and rSeries platforms.
3.3.5
3.3.4
3.3.3
3.3.2
Full Migration journey:
- Add a mitigation for unsupported LAPC on VE BIG-IPs (https://support.f5.com/csp/article/K85674611)
- Add a mitigation for an error happening when attempting to load a virtual containing HTTP3 profiles on 15.1.5 destination devices (https://cdn.f5.com/product/bugtracker/ID1080581.html)
- Allow longer platform codes to handle non-standard identifiers like 'Gemini'
- Add a list of warnings to the mitigations report
3.3.1
Full Migration journey:
- Add FIXLL profile parity gap mitigation for VELOS and rSeries
- Add Tunneling parity gap mitigation for VELOS and rSeries
- Modify RoundRobin mitigation to fix loading issue on rSeries caused by a dag-ipv6-prefix-len option
- Add a warning about only experimental support for HTTP3 on rSeries if such config is present in config
- Note that due to bug https://cdn.f5.com/product/bugtracker/ID1080581.html loading some configurations containing HTTP3 profiles may still fail. A mitigation will be added in a future release.
3.3.0
Full Migration journey:
- Add initial support for migrations onto rSeries tenants. More parity gap handling to be implemented in a future release
Application Service journey:
- Modified data structure to optimize operations on tenants, apps and virtuals. This change will require any already existing working directory to be recreated
- Fix the preview flow used when a qkview is provided as input instead of UCS
- Remove
auth partition
objects from the default application merging configuration - Fix ignoring
net
objects when deciding which virtuals to merge into a single application
3.2.4
Application Service Migration:
- Allow dots in application and tenant names