[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: inheriting enviroment variables by hooks

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Thu, 23 Nov 2017 17:32:21 +0100

On Thu, Nov 23, 2017 at 4:12 PM, <marcin_at_rhodecode.com> wrote:
>
> Hi Johan,
>
> I didn't know about that setting thanks for the pointer.
>
> However It looks like it's a way to set an alternative path to the hooks-env file. Which is global per repository. What we're trying to solve is to have a dynamic env that would inherit some variables per request. e.g IP address of client who is doing svn commit. There are bunch of stuff we'd like to pass along.

It seems that's not possible currently (I've checked with some other
devs on #svn-dev on freenode IRC). There are some httpd modules that
support injecting "environment variables" (in the httpd definition of
that term [1]), but mod_dav_svn doesn't. If you need this, this would
have to be discussed / developed as a new feature, I believe. If
you're interested in that, you're very welcome to drive such a feature
(starting by discussing what it should look / behave like). We're
always looking for new contributors ;-).

One other suggestion that came from Stefan Sperling on IRC was:
"ephemeral properties". These are some properties that are
automatically injected by mod_dav_svn as special properties in a
transaction, available in the pre-commit hook, but automatically
removed when the transaction gets promoted to a revision. Currently
there are two such properties:

    svn:txn-client-compat-version
    svn:txn-user-agent

See svn_props.h [2].
But I'm guessing those two existing properties are not sufficient for you.

[1] http://httpd.apache.org/docs/current/env.html
[2] http://svn.apache.org/viewvc/subversion/trunk/subversion/include/svn_props.h?revision=1718912&view=markup#l685

-- 
Johan
Received on 2017-11-23 17:33:02 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.