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

put-file version issue #64

Open
pwait opened this issue Jan 11, 2017 · 1 comment
Open

put-file version issue #64

pwait opened this issue Jan 11, 2017 · 1 comment

Comments

@pwait
Copy link

pwait commented Jan 11, 2017

Apparent issue relating to versioning of creds (less than 10, and more recent than 2016), see below example, where creds from months ago were updated with put-file, succesfully, but retrieval of creds somehow defaults to a version that seemingly doesn't exist.

This is run off from a windows machine via powershell through CMDer.

λ  .\unicreds -r ap-southeast-2 -p saml get license
LICENSE 66666666 2016.03 31-mar-2016 uncounted
  hostid=66666666 share=66666666 client_cache=66666666 customer=66666666
  akey=66666666 options=nodes=0,links=0,zones=0,mp=1,v=0
  _ck=66666666 sig="66666666"


λ  .\unicreds -r ap-southeast-2 -p saml get license1 3
   ⨯ failed                    error=Secret Not Found

λ  .\unicreds -r ap-southeast-2 -p saml get license1 2
LICENSE 66666666 2017.12 31-dec-2017 uncounted
  hostid=66666666 share=66666666 client_cache=66666666 customer=66666666
  akey=66666666options=nodes=0,links=0,zones=0,mp=1,v=0
  _ck=66666666 sig="66666666"


λ  .\unicreds -r ap-southeast-2 -p saml get license1 1
   ⨯ failed                    error=Secret Not Found
@wolfeidau
Copy link
Contributor

heya have you had a read over https://github.com/Versent/unicreds#auto-versioning to see if this is related to this issue we sorted out recently.

Cheers.

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