From 8fd0d725f718a30eed2d19b68abac7b26242f31e Mon Sep 17 00:00:00 2001 From: "benjamin.baker" Date: Tue, 25 Aug 2026 16:53:51 -0400 Subject: [PATCH] pin computers migration head to azurefields after Entra field merge The merge of the Entra device-identity work added computers 0002/0003 migrations, advancing the computers head past its anchor. Update the expected-head guard to match so upgrade-all stays green. --- tests/test_plugin_migrations.py | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tests/test_plugin_migrations.py b/tests/test_plugin_migrations.py index e4ef3976..2867c549 100644 --- a/tests/test_plugin_migrations.py +++ b/tests/test_plugin_migrations.py @@ -46,6 +46,10 @@ CUTOVER_PLUGINS = ( # stamp '0001anchor'; measuringtools stamps its real baseline id. EXPECTED_HEAD_REVISION = {plugin: f'{plugin}0001anchor' for plugin in CUTOVER_PLUGINS} EXPECTED_HEAD_REVISION['measuringtools'] = 'measuringtools0001baseline' +# computers adds the Entra/Azure device identity columns (azuredeviceid, then +# azureobjectid + azuredevicecategory) on top of its anchor, so its head is not +# the f-string default. +EXPECTED_HEAD_REVISION['computers'] = 'computers0003azurefields' # backups is also post-cutover: its 0001 really creates backuprevisions, and # 0002 adds lastseenat - when a config was last CONFIRMED unchanged, which dedup # otherwise throws away.