This PR has the following changes to source plugin(s) tables:

• ⚠️ BREAKING CHANGE: Table aws_cloudfront_cache_policies: column arn removed from table
• ⚠️ BREAKING CHANGE: Table aws_cloudfront_cache_policies: primary key constraint added to column account_id
• ⚠️ BREAKING CHANGE: Table aws_cloudfront_cache_policies: primary key constraint added to column id

As a side effect this would also break the resources view for this type. Is this a customer issue?

As a side effect this would also break the resources view for this type. Is this a customer issue?

This is a field we made up so it is not like users would be able to do anything with this field...

As a side effect this would also break the resources view for this type. Is this a customer issue?

This is a field we made up so it is not like users would be able to do anything with this field...

Yeah, but if there's no arn column a resource is not listed in the resources view. Granted this is the shortcoming of the resources view (lack of a better formed SQL) I was just wondering if this was an issue with any of our users or a general cleanup of sorts.

Even though it's made up, it's still a breaking change to remove it, and like @disq mentioned will cause it to disappear from the resources view, so I think we can leave it in place for now.