[rudder-dev] adding feature to a technique

[Michael Gliwinski]

On Tuesday 05 Feb 2013 13:51:50 Jonathan Clarke wrote:
> On 05/02/13 13:40, Michael Gliwinski wrote:
> > I know, it's hard.  I thought about it some more and the only thing I
> > could come up with that would preserve being able to version each
> > technique individually was to split the repository so each technique
> > has it's own, but that's probably a maintenance nightmare :|
> 
> That is actually something we have been considering. This could make
> sense if third parties decide to create and maintain Techniques, and
> want to keep the "code" in their own source repository (imagine some
> tool, like ElasticSearch or Redmine or something, decides to create a
> Technique for Rudder to make it easier for people to install their tool,
> but want to maintain control over the Technique to be able to upgrade it
> for their customers/users/etc).

Yes, that sounds very useful.  You could even have that aggregated in a 
TechiniqueForge of some sort ;)

> I think last time we discussed it, we too decided it's the only way to
> have versioning per-Technique. But to make it really easy for users that
> don't care about changing Techniques, we should present a unique git
> repository that assembles all the individual ones (sort of a "aggregated
> proxy view").

Do you mean you'd pull the various techniques together for a release or 
provide an automatically updated aggregate repo?

> This is where things get complicated, because the "git way" to do this
> is via git-submodules, but they're a bit iffy... So we were considering
> setting up some scripts to automate this, so that everytime an
> individual Technique repo gets updated, we git clone it, and commit it
> into the "unique" repo. Each directory would be a git clone from the
> individual repos, and thus conserve versioning info (git supports one
> repo inside another).
> 
> So, this is a possibility. It would involve quite a bit of work in the
> Rudder web interface to be able to get Technique versions from git
> instead of the filesystem, but it's not impossible. What do you think
> about this approach?

That sounds really really good :)  Definitely opens up lots of possibilities.

Regarding source of version information, wouldn't you want the configuration-
repository in Rudder installations to still store techniques in versioned 
directories, so that user is able to select which version to use?


**********************************************************************************************
The information in this email is confidential and may be legally privileged.  It is intended solely for the addressee and access to the email by anyone else is unauthorised.
If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.
When addressed to our clients, any opinions or advice contained in this e-mail are subject to the terms and conditions expressed  in the governing client engagement leter or contract.
If you have received this email in error please notify support at henderson-group.com

John Henderson (Holdings) Ltd
Registered office: 9 Hightown Avenue, Mallusk, County Antrim, Northern Ireland, BT36 4RT.
Registered in Northern Ireland
Registration Number NI010588
Vat No.: 814 6399 12
*********************************************************************************