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
KeyError with file.managed HTTPS source #28477
Comments
@anlutro I'm just holding that PR for another day to see if @jacksontj pops by to offer any insight. If not, I'll merge it and we can close this. Thanks for your patience. |
Sure, no problem. On Tue, 3 Nov 2015 16:39 Mike Place notifications@github.com wrote:
|
This way we have a consistent return method that some interal callers (fileclient) who don't care about the decoding of the message can just use. Fixes saltstack#28477
Another one... sigh. Well I just submitted #28573 with an attempt to fix this whole situation. The problem is that salt.utils.http has a really... complicated interface ;) The lack of tests on it makes is complicated to fix stuff-- since more often than not we break something else. I have an issue open elsewhere to rewrite/simplify/remove that library, but for now we'll continue whack-a-mole :/ |
@jacksontj Does #28573 supercede this PR or were you thinking they would both be merged? |
Oh, I didn't even see the other PR (sorry about that). From looking at it, I think my PR would probably cover this better. The eternal problem we're running into here is that all the HTTP libraries have very different interfaces so I tested locally with requests and tornado, so we should be covered? :/ |
If @anlutro is fine with it then, I'll close his and merge yours when the test finishes. Thanks @jacksontj |
Seems fine to me! I'll be able to verify that it works with my setup On Wed, 4 Nov 2015 17:37 Mike Place notifications@github.com wrote:
|
I don't have requests or tornado. My issue was with a sha1 hash file that On Wed, 4 Nov 2015 17:46 Thomas Jackson notifications@github.com wrote:
|
Seems to work fine now 👍 |
State:
Relevant part from the log:
Versionreport:
The text was updated successfully, but these errors were encountered: