Skip to content

Conversation

jrafanie
Copy link
Member

Opened as a followup to #41 since Pathnames were not supported in commands with no parameters and when used a parameter options.

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling cef1230 on jrafanie:pathname_support into 6c49753 on ManageIQ:master.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this backwards? The key part of a key/value pair is the command line option itself (the "--whatever") Does it make sense to have a path name on the key side?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Fryguy This example is contrived but I could see you running:

LinuxAdmin.run("/bin/some_script.sh", :params => {"/usr/bin/ruby" => nil})

If you wanted to use a Pathname instead of a String and it's not coming from user input, then I can imagine wanting to do this.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Fryguy what do you think?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jrafanie yeah, I think it's an ok test, although it is contrived, like you said. Basically, we are showing we can support anything as a key parameter.

Fryguy added a commit that referenced this pull request Aug 28, 2013
@Fryguy Fryguy merged commit a958afe into ManageIQ:master Aug 28, 2013
@jrafanie jrafanie deleted the pathname_support branch March 22, 2017 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants