Issue with aws_asset_inventory transformation always showing region as unavailable

hi, i am having an issue with the aws_asset_inventory transformation. I am not familiar with dbt, but I have been trying to dig into it, and for the life of me, I can’t figure this out.

When running the transformation, every item in the aws_resources view shows the region as ‘unavailable’. Based on the SQL, it looks at the source table to see if that column exists and then sets it based on that logic. When I run the SQL statements directly in Postgres, it is properly detecting some as 1 and some as 0, but when run with dbt, it always inserts unavailable.

Is anyone else having a similar issue? Is this transform used by anyone else here?

Hi @cunning-hare :wave: Thanks for opening an issue (I’m assuming this is you) and suggesting a fix.

You can track the issue here. We will release a fix for the asset inventory soon, and I will let you know here once it’s released.

The new version is v2.2.7. You can find the details here. This should fix the issue you encountered.

Let me know if you have any more issues or if this did not fix it!