-
Notifications
You must be signed in to change notification settings - Fork 74
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
version.locked? method returns incorrect value of true for unlocked version #47
Comments
I just noticed that some of my upload scripts are behaving the same way, where getting the latest version shows that it's unlocked, but when I inspected the
But when I look at
Haven't done more digging than that, but I'm seeing the same behavior and am glad it's not just me. Creating a new clone in the Fastly UI was how I got the upload scripts to work again for me as well. Edited to add that I'm seeing this on gem version 1.4.2 on both a Mac and CentOS, not that I think the OS matters all that much. |
One more thing (I promise to start coalescing my updates 😄 ) - when calling the API directly, the version is returned as locked. I looked through the history of Version.rb, and right before this ticket was made, a commit removed Here's the commit where it was removed: And my
Corresponding API call:
|
When calling Version.locked? on an unlocked / freshly cloned version the response is always true regardless of actual state.
The only time this is not true is if the version was created / cloned by this instance of Fastly.
The text was updated successfully, but these errors were encountered: