Automated IdP Installation
Nathan Mische
nmische at gmail.com
Tue Sep 13 18:25:24 BST 2011
The problem is the build doesn't check for property existence before
prompting the user for input. That is what I added to the build.
Here is a typical change I made:
before:
<input message="Where should the Shibboleth Identity Provider software
be installed?" addproperty="idp.home.input"
defaultvalue="${idp.home}"/>
<var name="idp.home" value="${idp.home.input}"/>
after:
<if>
<isset property="idp.home.input" />
<then>
echo message="Installing the Shibboleth Identity Provider
software to: ${idp.home.input}."/>
</then>
<else>
<input message="Where should the Shibboleth Identity Provider
software be installed?" addproperty="idp.home.input"
defaultvalue="${idp.home}"/>
</else>
</if>
<var name="idp.home" value="${idp.home.input}"/>
--Nathan
On Tue, Sep 13, 2011 at 1:17 PM, Peter Schober
<peter.schober at univie.ac.at> wrote:
> * Nathan Mische <nmische at gmail.com> [2011-09-13 19:10]:
>> We are looking to automate our IdP setup, however we hit a snag with
>> the installer's Ant build. The current Ant build requires input from
>> the user. To get around this I've hacked up the Ant build such that if
>> you define properties in install.properties the build no longer
>> requires user input.
>
> Couldn't you run `./install.sh -propertyfile foo.properties` without
> requiring a patch?
> Or define individual properties with `./install.sh -Dfoo=bar` ?
> -peter
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>
More information about the users
mailing list