Skip to content
This repository has been archived by the owner on Aug 16, 2022. It is now read-only.

Handle timestamps/datetimes uniformly across all resources #813

Closed
andrewthetechie opened this issue May 1, 2022 · 0 comments · Fixed by #891
Closed

Handle timestamps/datetimes uniformly across all resources #813

andrewthetechie opened this issue May 1, 2022 · 0 comments · Fixed by #891
Assignees
Labels
bug Something isn't working

Comments

@andrewthetechie
Copy link
Contributor

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

@andrewthetechie andrewthetechie added the bug Something isn't working label May 1, 2022
@zagronitay zagronitay self-assigned this May 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants