[chef] Re: Re: Automating Gerrit Ssh Keys


Chronological Thread 
  • From: Stephen Nelson-Smith < >
  • To:
  • Subject: [chef] Re: Re: Automating Gerrit Ssh Keys
  • Date: Fri, 10 Jan 2014 00:52:34 +0000

What did you do about flushing cache?  Maybe cache gets flushed if you restart gerrit anyway... 


On 9 January 2014 20:44, 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



--
Stephen Nelson-Smith,
Founder, Principal Consultant,
Atalanta Systems Ltd,
Web: http://agilesysadmin.net
Twitter: @lordcope
Skype: atalanta.systems
Direct: +44 (0) 1329 550203
Mobile: +44 (0) 7917 101919

Atalanta Systems: The Agile Infrastructure Enablers
http://atalanta-systems.com



Archive powered by MHonArc 2.6.16.

§