[chef] Re: knife ec2 - knife.rb takes precedence over command line options

[AJ Christensen < >]

I've had more than one occasion where it's impossible to set an option
via the knife.rb, only the CLI. There are a number of issues here. I
have occasionally resorted to medium-Ruby magic to inject my custom,
overridable settings into Knife.

Would definitely like to see both sides of this blade sharpened a little.

--AJ

On 26 April 2012 20:13, Nick Peirson 
<
 >
 wrote:
> Hi All,
>
> Is this the expected behaviour? I've raised it as an issue in github
> (https://github.com/opscode/knife-ec2/issues/41), but thought I'd seek
> others opinions here as well. It seems to prevent knife ec2 commands from
> being scripted effectively if there are entries in knife.rb.
>
> Use case is having defaults in knife.rb to spin up instances quickly while
> testing things without having to type a command line as long as your arm,
> but occasionally want a different AMI or to start an instance in a different
> AZ by quickly overriding on the command line. At the moment it's a case of
> having to change the knife.rb, run the command, change it back or,
> alternatively, leave the options out of knife.rb and always pass as command
> line arguments.
>
> It surprises me that this isn't affecting anyone else, so I'm wondering if
> I'm doing something to cause this behaviour?
>
> Cheers
> Nick
>