Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ECR gives wrong creation timestamp #34

Closed
whitlockjc opened this issue Jun 23, 2016 · 2 comments
Closed

ECR gives wrong creation timestamp #34

whitlockjc opened this issue Jun 23, 2016 · 2 comments

Comments

@whitlockjc
Copy link
Contributor

Whenever I create a new image, the creation date comes back wrong. Example:

{"created":"1970-01-01T00:00:00Z","imageId":"sha256:534b41ca0c2ca5ad2728da9cdd2a9eda90ef47a9c78646ff85147a15b7adda76"}
tnine pushed a commit that referenced this issue Jun 24, 2016
Updates revision to 1.8
@noahdietz
Copy link
Contributor

noahdietz commented Jul 21, 2016

@whitlockjc

The time stamp being read from image.Created and returned to the user is never initialized for the returned object in the called function thus the default value is used for the time.Time member variable, which is always Year 1 Day 1 of Month 1

Update
Doesn't look like ECR provides a creation time stamp, in the API

@noahdietz
Copy link
Contributor

noahdietz commented Jan 23, 2017

The information provided when retrieving an imported application will be addressed in #75

The current implementation doesn't support a timestamp. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants