mirror of
https://github.com/fleetdm/fleet
synced 2026-05-04 05:48:26 +00:00
38b8c9cc58
#15555 Probably the best way to review this is commit by commit: - First commit does the actual moving. - Second commit fixes golangci-lint issues (in the least effort way to avoid refactoring or rearrangement of some of the code). - Third commit moves a printf to before the migration step is executed. In the past some customers hitting migration issues (like migration steps hanging or taking long to execute) and wanted to know which one was it. The only way to know was to look at the repository and looking for the next migration after the last one logged. Checks: - [X] Manual QA for all new/changed functionality Manual tests: - `make fleet && make db-reset`. - Adding a new migration via `make migration name=Foobar` and then running `./build/fleet prepare db`. - Enrolling a new device to Fleet (smoke test). |
||
|---|---|---|
| .. | ||
| 20161229171615_InsertBuiltinLabels.go | ||
| 20170223171234_UpdateBuiltinLabels.go | ||
| 20170301093653_AddAllHostsToAllHostsLabel.go | ||
| 20170314151620_FixCentosLabel.go | ||
| 20181119180000_Placeholder.go | ||
| 20210330130314_UpdateBuiltinLabels.go | ||
| 20210806135609_AddAllLinuxBuiltInLabels.go | ||
| 20210819120215_ChangeTeamScheduleNames.go | ||
| 20230525175650_InsertChromeBuiltInLabel.go | ||
| migration.go | ||
| README.md | ||
Data Migrations
Data migrations are now deprecated, and any data changes (DML statements - Data Modification Language) should be done in standard "tables" migrations, alongside any table (DDL statements - Data Definition Language) changes.