You can create a file called .whirr-test.properties in your home
directory and set whirr.image-id in there to the value you want. Then
do
mvn verify -Pintegration -DargLine="-Dwhirr.test.provider=aws-ec2
-Dwhirr.test.identity=$AWS_ACCESS_KEY_ID
-Dwhirr.test.credential=$AWS_SECRET_ACCESS_KEY
-Dconfig=.whirr-test.properties"
Tom
On Fri, Sep 21, 2012 at 12:36 PM, Steve Loughran <ste...@hortonworks.com> wrote:
> Is there a policy on specifying machine instances?
>
> I have a specific AMI I want to test against, and have set up the
> test.properties file to be driven by a system prop
>
> whirr.image-id=${sys:whirr.test.image-id}
>
> then I can use -Dwhirr.test.image-id=us-west-2/ami-1234
>
> I don't think this is ideal, really you'd want a check that had a default
> value and allowed people to override it if they really wanted to.
>
> What can be done here (this is for something I do plan to submit, the AMI
> is an AMAZON-LINUX image brought up to date with patches and the right java
> version pre-installed. The official AMIs lag security-wise.
>
> -Steve
