You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2022. It is now read-only.
Describe the bug
In some resources, timestamps are treated as integers. In others, they're treated as strings. In some places, they're treated as timestamps
Expected Behavior
All timestamps in aws services fetched by cloudquery-provider-aws are expressed in the same schema.
Steps to Reproduce
Setup cloudquery, initialize the database and inspect the schemas of aws_ec2_images, aws_sqs_queues, and aws_sns_topics.
There are many other examples as well
Possible Solution
My preferred solution would be that all timestamps/datetimes are all treated as timestamps.
Provider and CloudQuery version
Version: 0.22.7 Commit: fb5a1447e0851d96af0fb7d522585bf78566ff3f Date: 2022-04-19T08:55:30Z v0.11.1
Additional Context
No response
The text was updated successfully, but these errors were encountered: