Fortinet upgrade intelligence
FortiUpgrade
Query recommended paths, enrich every step and monitor useful version, vulnerability and notification signals.
01
The problem
A firmware upgrade is more than a sequence of versions: the official path, builds, known issues, behaviour changes and relevant vulnerabilities all need to be checked.
02
My role
Business requirements, security and persistence rules, operator workflow validation, and oversight of changes through production delivery.
03
Key decisions
- Prefer the Fortinet source whenever available and disclose cache fallback explicitly.
- Isolate collectors so a failing source stays visible without erasing the latest confirmed data.
- Persist checkpoints and the outbox before delivery to prevent lost or duplicate notifications.
- Publish a traceable image and keep the previous artifact available for rollback.
04
Demonstrable outcome
The delivered release runs on the VPS with a healthy web service and an active scheduler. Its reference delivery validated 330 Python tests, 16 browser scenarios, the image build and local/public smoke tests. Paths remain operational guidance and must be revalidated against the official source.
05
Technologies
AI assistants accelerated parts of the design and development work. Network/security decisions, acceptance criteria, testing and validation remain human-led and human-verified.