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.

Sign up for GitHub

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

Jump to bottom

compatibility: bottlerocket metadata uses microseconds in expiry #1857

Open
jku opened this issue Feb 11, 2022 · 1 comment
Open

compatibility: bottlerocket metadata uses microseconds in expiry #1857

jku opened this issue Feb 11, 2022 · 1 comment

Comments

@jku
Copy link
Member

jku commented Feb 11, 2022 •
edited
Loading

We have recently started to not accept microseconds in the expiry in an effort to be spec compliant.

Testing ngclient against bottlerocket metadata fails because they use microseconds:
https://updates.bottlerocket.aws/2020-07-07/aws-k8s-1.16/x86_64/timestamp.json

  • could file an issue in awslabs (though I'm not sure if this is their problem or not)
  • Maybe reconsider if we are too strict and should accept this input in deserialization (even if not when expiry is set in code)?
@jku jku mentioned this issue Feb 11, 2022
Closed
@jku
Copy link
Member Author

jku commented Feb 14, 2022

could file an issue in awslabs

webern was proactive: awslabs/tough#447

@jku jku changed the title maybe compatibility issue: bottlerocket metadata uses microseconds in expiry compatibility: bottlerocket metadata uses microseconds in expiry Feb 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jku