After version 0.8.0 of Cognite Toolkit, table definitions in .Database.yaml files lead to database deletion attempts

When attempting to upgrade from version 0.7.237 to 0.8.33, we saw the following error in our deployment log

  ERROR (ResourceDeleteError): Failed to delete raw databases due to API error: 
Request failed with status code 400: Tried to delete non-empty databases 
raw_miros non-recursively.
The request body and response has been written to 
deploy_logs_2026-04-24/2026-04-24T15_28_00.297618+00_00.json for debugging 
purposes.

The raw_miros database is referenced in input files with the .Database.yaml file extension and with contents like this

- dbName: '{{raw_db_name_prefix}}_miros'
  tableName: header_alv
- dbName: '{{raw_db_name_prefix}}_miros'
  tableName: header_iaa
- dbName: '{{raw_db_name_prefix}}_miros'
  tableName: header_ska
...

Based on dry runs, it seems like we can avoid database deletion attempts by renaming the files to have the .Table.yaml file extension.

The YAML reference page for Cognite Toolkit states

RAW table configuration filenames must end with Table, for example, my_table.Table.yaml. Database configuration filenames must end with Database, for example, my_database.Database.yaml.

Although the reference does not present an example of a database configuration, I believe a database configuration only has the dbName property, not a tableName property like above. The input file worked as intended in version 0.7.237 and earlier.

It is difficult to see how Cognite Toolkit’s attempt to delete the RAW database in version 0.8.33 is reasonable based on the input files, so I suspect this constitutes a bug even if we should rename our files with the .Table.yaml file extension.