command line argument switches should override configuration file information in knife.rb

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 0.9.8, 0.10.4
  • Fix Version/s: None
  • Component/s: Knife
  • Labels:
    None

Description

knife ec2 server create -A DEADBEEF

should override .chef/knife.rb's

knife[:aws_access_key_id] = "FOOBAR"

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Bryan McLellan [Opscode] added a comment -

https://github.com/opscode/chef/pull/20

Show
Bryan McLellan [Opscode] added a comment - https://github.com/opscode/chef/pull/20
Hide
Permalink
Nick Peirson added a comment -

Unfortunately that pull request (https://github.com/opscode/chef/pull/20) doesn't seem to be related to this ticket, as the request adds new fields rather than changing the precedence of existing fields.

Show
Nick Peirson added a comment - Unfortunately that pull request ( https://github.com/opscode/chef/pull/20 ) doesn't seem to be related to this ticket, as the request adds new fields rather than changing the precedence of existing fields.
Hide
Permalink
Nick Peirson added a comment -

While this ticket hasn't got much love, there's clearly a need to resolve it from the response from people on the chef mailing list: http://lists.opscode.com/sympa/arc/chef/2012-04/msg00425.html

Many people are working round this problem in various ways and it's undoubtedly causing confusion for people, particularly new users.

As an initial triage step, can the documentation on knife configuration (http://wiki.opscode.com/display/chef/Knife#Knife-ConfiguringYourSystemForKnife) be updated with a warning to flag this potential gotcha for new users?

Suggested wording:
"WARNING: Precedence of knife configuration option parsing is not consistent, particularly within plugins. This may cause command line options to be ignored in favour of options set in knife.rb. Also note that not all options are read from both command line and knife.rb"

Show
Nick Peirson added a comment - While this ticket hasn't got much love, there's clearly a need to resolve it from the response from people on the chef mailing list: http://lists.opscode.com/sympa/arc/chef/2012-04/msg00425.html Many people are working round this problem in various ways and it's undoubtedly causing confusion for people, particularly new users. As an initial triage step, can the documentation on knife configuration ( http://wiki.opscode.com/display/chef/Knife#Knife-ConfiguringYourSystemForKnife ) be updated with a warning to flag this potential gotcha for new users? Suggested wording: "WARNING: Precedence of knife configuration option parsing is not consistent, particularly within plugins. This may cause command line options to be ignored in favour of options set in knife.rb. Also note that not all options are read from both command line and knife.rb"
Hide
Permalink
Daniel DeLeo added a comment -

This is fixed in Chef 11, not sure of the ticket number the work got filed under.

Show
Daniel DeLeo added a comment - This is fixed in Chef 11, not sure of the ticket number the work got filed under.

People

  • Assignee:
    Unassigned
    Reporter:
    Sean OMeara
Vote (5)
Watch (6)

Dates

  • Created:
    Updated:
    Resolved: