fix: make relay catalog safe for existing routes
This commit is contained in:
1 parent
2d7255a5d3
commit
1a57de5bf9
2 files changed
+38
-19
No files matched your search
+6
-2
@@ -69,8 +69,12 @@ class PlatformAdminPostgresTest {
|
||||
jdbc.update("INSERT INTO users(id,account,account_kind,password_hash,display_name) VALUES (?,'legacy_member','username','not-a-login-hash','Legacy Member')", legacyUser);
|
||||
jdbc.update("INSERT INTO platform_api_keys(id,user_id,name,key_prefix,key_hash,model_ids) VALUES (?,?,'Legacy Key','test-prefix',?,?::jsonb)", legacyKey, legacyUser, "a".repeat(64), legacyGrants);
|
||||
Flyway.configure().dataSource(base).schemas(schema).defaultSchema(schema).load().migrate();
|
||||
assertEquals(legacyIds, jdbc.queryForList("SELECT id FROM model_catalog ORDER BY id", String.class));
|
||||
assertEquals(legacyIds, jdbc.queryForList("SELECT logical_model_id FROM model_catalog ORDER BY id", String.class));
|
||||
// V14 adds relay definitions/routes. Existing legacy routes and grants must survive
|
||||
// alongside the expanded catalog rather than making the catalog remain seven rows.
|
||||
assertTrue(jdbc.queryForList("SELECT id FROM model_catalog ORDER BY id", String.class).containsAll(legacyIds));
|
||||
for (String legacyId : legacyIds) {
|
||||
assertEquals(legacyId, jdbc.queryForObject("SELECT logical_model_id FROM model_catalog WHERE id=?", String.class, legacyId));
|
||||
}
|
||||
assertEquals(json.readTree(legacyGrants), json.readTree(jdbc.queryForObject("SELECT model_ids::text FROM platform_api_keys WHERE id=?", String.class, legacyKey)));
|
||||
context = new AnnotationConfigApplicationContext();
|
||||
sender = new TestSender();
|
||||
|
||||
Reference in new issue
Block a user