[chef] Re: Re: Re: Registration when an existing client.pem is present?

[Morgan Blackthorne < >]

Yeah, I was just checking if there was any other ways to handle the situation, but in the end an AMI prep script seems like the easiest and least hacky solution :)

--

~*~ StormeRider ~*~

"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."

(from Smallville Season 6x1: "Zod")

On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS

On Thu, Jun 6, 2013 at 6:57 AM, Cassiano Leal < " target="_blank"> > wrote:

Is it that big a deal to regenerate the AMI after deleting the key? It seems to me that this would be the easiest and least hacky way out. :)

- cassiano

On Thursday, June 6, 2013 at 10:46, Steven Danna wrote:

On 6/5/13 1:39 AM, Morgan Blackthorne wrote:

I'm guessing that because the client keys can be shared that the answer

to this question is no, but is there a way to set things so that if the

client name does not exist that it will perform registration instead of

trying to use the old key?

It would be possible to create a patch to Chef that checked if the

client existed using the validator client before attempting to use the

client.pem. I'm not a huge fan of adding uses of the validator client

into Chef, however.

Or is there a specific error code that I can trap for when doing this

and detect that it failed?

You might be able to do something with the event dispatch system. There

is a node_load_failed event that you could potentially hook into.

Alternatively, it is likely possible to catch the HTTP 401 errors in an

error handler.

Cheers,

Steven

--

Steven Danna

Systems Engineer, Opscode, Inc

GPG Key: http://stevendanna.github.com/downloads/code/public.key