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

Ignore unknown properties when deserializing ExecCredential #1280

Merged
merged 2 commits into from
Nov 30, 2018

Conversation

seshness
Copy link
Contributor

aws-iam-authenticator token --cluster-id <cluster-id> returns a JSON blob of the form

{
  "kind": "ExecCredential",
  "apiVersion": "client.authentication.k8s.io/v1alpha1",
  "spec": {},
  "status": {
    "expirationTimestamp": "2018-11-28T02:24:39Z",
    "token": "<some token>"
  }
}

This fails to deserialize in ExecCredentialStatus. There is a TODO to add some fields, including expirationTimestamp, but this is a temporary stopgap to avoid requiring those fields.

`aws-iam-authenticator token --cluster-id <cluster-id>` returns a JSON blob of the form
```
{
  "kind": "ExecCredential",
  "apiVersion": "client.authentication.k8s.io/v1alpha1",
  "spec": {},
  "status": {
    "expirationTimestamp": "2018-11-28T02:24:39Z",
    "token": "<some token>"
  }
}
```
This fails to deserialize in `ExecCredentialStatus`. There is a TODO to add some fields, including `expirationTimestamp`, but this is a temporary stopgap to avoid requiring those fields.
@centos-ci
Copy link

Can one of the admins verify this patch?

@rohanKanojia
Copy link
Member

ok to test

Copy link
Member

@rohanKanojia rohanKanojia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, Could you please add a line to CHANGELOG.md regarding this?

Copy link
Member

@oscerd oscerd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, we just need a changelog entry

@oscerd
Copy link
Member

oscerd commented Nov 28, 2018

Ok to test

@rohanKanojia
Copy link
Member

[merge]

@jglick
Copy link
Contributor

jglick commented Jan 3, 2019

Amends #1224 FTR. I saw no such errors when testing my original patch; not sure what the difference is between my environment and others’.

@nightswimmings
Copy link

I'm getting this with latest 4.4.1 version of the fabric8-maven-plugin.

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

Successfully merging this pull request may close these issues.

7 participants