-
Notifications
You must be signed in to change notification settings - Fork 28
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
Use gha-puppet again #310
Use gha-puppet again #310
Conversation
For complete context, there are now PRs up: voxpupuli/puppet_metadata#108 & voxpupuli/gha-puppet#42 |
Note to self: also support |
Something is different with curl: When I run it manually on EL8: # curl --silent --write-out '%{stderr}Response-Code: %{response_code}\n' https://ekohl.nl
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
curl: unknown --write-out variable: 'stderr'
Response-Code: 301
# curl --silent --write-out '%{stderr}Response-Code: %{response_code}\n' https://ekohl.nl > /dev/null
curl: unknown --write-out variable: 'stderr'
# curl --silent --write-out '%{stderr}Response-Code: %{response_code}\n' https://ekohl.nl 2> /dev/null
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
Response-Code: 301 So now I wonder how this ever worked. #311 is passing, but now I can't explain why. Edit: the only thing I can imagine is that the previous helpers somehow mixed stdout and stderr together where now it's split. |
Integrated in #309 now that all the bits are in. |
Following up: beaker-puppet hacked |
Great detective work! |
This is to test out some new workflows where we again rely on the common workflows but while also adding the option to test multiple versions.
Right now it's unknown if this concept works.