Config UUID is not being updated. #135
Description
We find an issue where the config_uuid for our dynamic table configurations does not update. Our infrastructure relies on these dynamic tables, and we update them by modifying the content of the JSON file used in our curl commands and also the bq table content.
Despite successfully executing the curl command with the updated JSON, the config_uuid remains the same as the initial configuration (keeping the first configuuid from the first request we did for that table). This prevents any changes from being reflected in the associated Dataplex aspects, as they appear to be linked to the original config_uuid.
- Steps to Reproduce:
- Create an initial configuration for a dynamic table using a curl command with a specific JSON file.
- Modify the content of the JSON file to update the dynamic table's configuration.
- Execute the curl command again with the updated JSON to apply the changes.
- Run a new job with a new job_uuid.
- Audit the configuration.
Expected Behavior:
A new config_uuid should be generated to reflect the changes made to the dynamic table's configuration. Subsequently, the Dataplex aspects should be updated based on this new configuration when a new job is run.
Current Behavior:
The config_uuid does not change from its initial value. As a result, even with a new job_uuid, the Dataplex aspects are not updated and retain the format from the initial configuration.
This is from oct 2
{
"textPayload": "Info: config already exists bf3xxxxx returning existing config",
"insertId": "xx",
"resource": {
"type": "cloud_run_revision",
"labels": {
"service_name": "tag-engine-api",
"configuration_name": "tag-engine-api",
"revision_name": "tag-engine-api-xx-7ht",
"project_id": "myproject",
"location": "us-central1"
}
},
"timestamp": "2025-10-02T15:19:50.281062Z",
"labels": {
"instanceId": "xxxx"
},
"logName": "projects/xxxxxx",
"receiveTimestamp": "2025-10-02T15:19:50.319456466Z"
}
This is from sept 23
{"config_status":"ACTIVE","config_type":"DYNAMIC_TAG_TABLE","config_uuid":"bf3xxx","creation_time":"Tue, 23 Sep 2025 19:51:50 GMT"},
And we change the json file and the tables but the changes didn't apply.
This issue also help him: juan.vallecilla@davivienda.com