You'll need to make sure yoh use add-pssnapin to load the vmware commands into the powershell session.
Steve
PowerCLI usually requires a special PowerCLI-enabled session. For instance, when I run powershell, i can't access powercli cmdlets, but must instead startup using the powercli icon (You can examine the shortcut to see whats being done in the background to load the powercli into the powershell console to get the new, special console.)Could it be that powercli cmdlets are not accessible in the "powershell only" console that beings executed in your resource call?On Tue, Sep 16, 2014 at 6:45 AM, Matt Ray < " target="_blank"> > wrote:If you run those commands within a recipe, use "chef-client -l debug"
and you should see the full output of the commands as they're run. My
hunch with shell commands is it's usually related to the environment
the commands are running in and the commands are returning a bogus
error code, so checking them as they run should provide a little more
clarity.
Thanks,
Matt Ray
Director of Partner Integration :: Chef
512.731.2218 :: " target="_blank">
mattray :: GitHub :: IRC :: Twitter
On Mon, Sep 15, 2014 at 11:03 PM, Ashutosh Narayan
< " target="_blank"> > wrote:
> Hello folks,
>
> I am implementing vCloud director using PowerCLI commands. Now I wish to
> execute those PowerCLI commands using Chef, it seems that the resources are
> executed properly but the commands on vCloud end are not running successfully.
> The PoweCLI scripts are running successfully when I execute them from
> PowerShell promt. I have used "powershell" and "execute" resources, they also
> run successfully, but there is no effect in the vCloud environment.
> Has anyone in the list has tried so ? Any help is appreciated.
>
> Thank you,
> Ashutosh Narayan
--Kenneth Barry
Archive powered by MHonArc 2.6.16.