Files

T

Lucas Manuel Rodriguez 60d8f51374 Move test/upgrade to tools/ to reduce security scanning noise (#49158 )

Two reasons:
- It's a testing/QA tool, so it should be under `tools/`
- Reduce security-noise because it's just an internal tool (all findings
under tools/ should be ignored).

Failing dependency review expected because of the security findings in
the docker Go packages. (Which can be fixed/updated when a patch is
issued but without urgency because this is an internal tool.)

## Testing

- [x] QA'd all new/changed functionality manually

Ran:
```
cd tools/upgrade
FLEET_VERSION_A=v4.87.1 FLEET_VERSION_B=v4.88.1 go test
```

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

## Summary by CodeRabbit

* **New Features**
  * Added an end-to-end upgrade test scenario across two Fleet versions.
* Added a Docker Compose-based upgrade environment (Fleet, MySQL, Redis,
osquery) with local TLS certs/keys and osquery flags.

* **Tests**
* Added automated Fleet readiness checks and host enrollment
verification before and after upgrade.

* **Chores / Security**
* Updated the database upgrade test workflow and Go module tooling for
the new upgrade test setup.
* Adjusted secret scanning allow-rules and refreshed Go dependencies for
the upgrade module.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-07-13 11:17:37 -03:00

433 B

Raw Permalink Blame History

Upgrade Tests

This tool can be used to test DB upgrades between two Fleet versions.

To run the tests, you need to specify the "from" and "to" versions, for example:

cd tools/upgrade
FLEET_VERSION_A=v4.16.0 FLEET_VERSION_B=v4.18.0 go test

Ensure that Docker is installed with Compose V2. To check if you have the correct version, run the following command

docker compose version
Docker Compose version v2.6.0

433 B Raw Permalink Blame History

Upgrade Tests

433 B

Raw Permalink Blame History