From 4201a2dc11b742db4bacc470f6eb806bc6ac53f8 Mon Sep 17 00:00:00 2001 From: Fabricio Duarte Date: Thu, 30 Jan 2025 18:07:50 -0300 Subject: [PATCH] Fix Usage job not executing successfully (#10244) * Add `api_key_access` to Usage account table * use the procedure in cloud_usage instead --- .../src/main/resources/META-INF/db/schema-42000to42010.sql | 1 + 1 file changed, 1 insertion(+) diff --git a/engine/schema/src/main/resources/META-INF/db/schema-42000to42010.sql b/engine/schema/src/main/resources/META-INF/db/schema-42000to42010.sql index 976ef217832..92e0dbb5b2a 100644 --- a/engine/schema/src/main/resources/META-INF/db/schema-42000to42010.sql +++ b/engine/schema/src/main/resources/META-INF/db/schema-42000to42010.sql @@ -22,6 +22,7 @@ -- Add column api_key_access to user and account tables CALL `cloud`.`IDEMPOTENT_ADD_COLUMN`('cloud.user', 'api_key_access', 'boolean DEFAULT NULL COMMENT "is api key access allowed for the user" AFTER `secret_key`'); CALL `cloud`.`IDEMPOTENT_ADD_COLUMN`('cloud.account', 'api_key_access', 'boolean DEFAULT NULL COMMENT "is api key access allowed for the account" '); +CALL `cloud_usage`.`IDEMPOTENT_ADD_COLUMN`('cloud_usage.account', 'api_key_access', 'boolean DEFAULT NULL COMMENT "is api key access allowed for the account" '); -- Modify index for mshost_peer DELETE FROM `cloud`.`mshost_peer`;