You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: