Initial implementation for custom_arguments passed to Fog. #7
Conversation
| @@ -30,6 +30,7 @@ def load_fog_gem | |||
|
|
|||
| def connection | |||
| add_api_endpoint | |||
| add_custom_arguments | |||
There was a problem hiding this comment.
Not sure what this gets us -- do you know of cases where initiating the Fog service connection with extra parameters gets us additional functionality?
|
So the idea here is that for every command, you can pass additional options -- these will not be validated, and may be ignored, and may cause unknown behavior. But the idea here is that if you know something about the underlying provider, you can still get the benefits of one-stop shopping with a chef + cloud provider integration -- no need to write a wrapper script to create vm's and then chef them up. To be sure we're on the same page, can you post an example command line (real-world) for say OpenStack -- e.g. knife openstack server create that lets us do something with openstack that we can't do currently with knife openstack but is supported by Fog? |
|
I have updated JIRA (OC- 10611) with a real time example for custom_arguments passed to Fog, that is not supported by knife-cloud. |
…dService, not just FogService.
|
Reopening new PR to opscode master |
Please confirm this approach.
Currently we pass the arguments with --custom-arguments "provider=openstack" format. Here provider is an actual attribute supported by Fog.
Thanks.