Wanis Fahmy

Found it, thanks alot

hey @pjungermann, apologies for not being active here, Should I rename the title and description of the issue?

iirc (https://github.com/backstage/backstage/issues/20718) was the initial issue that drove me to create this one

@efenner-cambia out of curiosity, are the entities removed if you're only archiving without renaming? If so, can you please share your config? it doesn't seem to work for us. see...

@efenner-cambia thanks for sharing the configs and the hint. I tried switching `validateLocationsExist` but it didn't help :/ The events for archiving are both published by github and also subscribed...

`@azure/identity` v4 is now released but i still needed to add a resolution in the package.json to make it run against node 20. running on backstage 1.20.3

@klesh seems that it's blocked by this: https://github.com/dbt-labs/dbt-core/issues/9491

+1

had the same issue with `parquet` format, the below workaround did the trick: `file_format = format("FORMAT_NAME =%s.%s.PARQUET", var.db_name, each.value.schema_name)

thanks for the detailed explanation @mhaley37! yea that's exactly what we're also facing. It would be nice if someone from the maintainers have a look