Per IRC conversations with Dustin. We need to be able to get a native windows executable version of certs.sh returned via getcert.cgi for our windows puppetize scripts. Options currently include simply returning a certs.bat file or possibly getting fancy and returning json objects. Backward compatibility should be incorporated so these functions should only be activated via new arguments. ( I.E. &windows=1&JSON=1 etc) with the current behavior being the default.
Compatibility isn't actually such a big deal - if we do this with JSON, then we can just adjust puppetize.sh in the same commit.
Created attachment 806042 [details] [diff] [review] bug917013.patch
As a reminder to myself, I'll need to update puppetize.sh on the DS servers.
Sorry first time I've had a tag for review. As a quick note this change will break the testing Mark is doing with puppett and my hacked script.
Comment on attachment 806042 [details] [diff] [review] bug917013.patch looks nice and simple. json objects can be parsed client side. I don't see any obvious errors.
Comment on attachment 806042 [details] [diff] [review] bug917013.patch In the attachment details, set the "review" flag to + (or - if it's not ready to land).
If you need to land this while I'm away, feel free. It should "just work" for kickstarts, and will need the puppetize.sh file copied to the DeployStudio servers in order to make OS X deploys work.
So, how/when shall we land this?
As a note to self, this will need a followon fix to the masterize process, which runs deployment_getcert.sh directly.
We're going to stick with the current status for the moment, until we have puppet running on Windows. Then, we'll swap in the new, JSON-reading vbs script (which isn't written yet) using puppet itself.
We really should land this at some point....
we can shipz this nao?
AIUI Q's working on this. I'll be happ to do the landing when it's ready.
json parsing vbs is still being worked on. stalled due to the fact that authentication seems to kill the json get.
Dustin please go ahead and land the patches. We are past the point that it affects Mark's testing and I can tweak the vbs as needed after the getcert.cgi lands.
Rail, will landing this make the spot-instance-creation stuff fail?
(In reply to Dustin J. Mitchell [:dustin] (I ignore NEEDINFO) from comment #17) > Rail, will landing this make the spot-instance-creation stuff fail? Yeah. We rely on the fact that the content returned by getcert.py is a shell script, which dumps certs to the files...
How difficult would it be to rework that to accept JSON? And how often does that happen -- do we need a downtime?
Actually, let's put this on hold. The way project X is looking, we may not be running puppet on windows (!).
We probably *should* land this now, with no change to any clients.
Q, is this moot now?