Upgrading the App

Here you will find any steps necessary to upgrade the App in your Nautobot environment.

Upgrade Guide

1. Read the release notes and back up the database and uploaded archives.
2. Prepare persistent private atlas storage if using the Operational Map.
3. Stop Nautobot web and worker services, then upgrade the package.
4. Run post-upgrade tasks with the database, original media, and private storage available.
5. Restart services and validate key TRAX workflows.

For an existing map installation, follow the private atlas migration instructions before restarting services. Container deployments must keep both storage mounts available to the migration/init container.

Upgrade to the latest release:

pip install --upgrade nautobot-trax

Upgrade to a specific version:

pip install --upgrade nautobot-trax==0.1.0

Apply migrations and clear caches:

nautobot-server post_upgrade

When using offline maps, verify storage from each web/worker instance:

nautobot-server check_map_storage

Migration 0012_operation_map_tile_sets adds optional operation basemap associations. Existing operations continue to use the available map selector until associations are configured. Missing archives are now excluded from that selector and return uncacheable 503 responses instead of tile 404s or stale 304s.

Upgrade Notes

• Pin the package version and review release notes before upgrading.
• The 0.1.x series can introduce schema or behavior changes before version 1.0.
• Operational Map archive processing requires Python 3.11 or later. Other TRAX functions retain the package's Python 3.10–3.13 requirement.
• Normal migration does not create the demo operator. For an existing demo, nautobot-server setup_operator_user refreshes its permissions, including Map Tile Set permissions, without resetting an existing password.