[chef] Re: Re: Automating Gerrit Ssh Keys

[Ranjib Dey < >]

i faced similar issues with jenkins plugin installation (auth enabled), whether to use the config files or use the api. i am using multiple stages/chef runs to do this. 

altering the underlying config store (database, or xml files) will work as long as Chef controls the credentials for those config stores.

On Thu, Jan 9, 2014 at 12:44 PM, Adam Jacob < " target="_blank"> > wrote:

I jammed the admin in the database directly. Then the api after.

On Jan 9, 2014 10:35 AM, "Stephen Nelson-Smith" < " target="_blank"> > wrote:

Ohai,

I find myself in a bit of a dependency cycle.  I want to be able to automate the creation of accounts and running of gerrit commands over ssh.  In the simplest case, I want to automate the creation of a non-interactive Jenkins user, but that's just a specific example of a general requirement.

As far as I can tell, there are three ways to get ssh keys for Gerrit users into Gerrit:

1) Upload them via the web interface

2) Supply them via the gerrit create-account command

3) Stick them directly in the database and flush the cache

I have issues with all 3:

1) This just really sucks.  Sure I can automate it, but… really?

2) This has a dependency problem - you need a user with an ssh key in the first place

3) This is a bit nasty, and so far I haven't found a way to flush the cache without using the ssh command, so has the same dependency issue

Have any of you chefs solved this?

S.

-- 

Stephen Nelson-Smith

@LordCope

http://www.agilesysadmin.net