RE: How do I run Azure powershell commands?

[stuartjdavies]

Hi,

How do I run Azure powershell commands?

Below is my script:

#r "../packages/FSharp.Management.0.1.1/lib/net40/FSharp.Management.dll"
#r "../packages/FSharp.Management.0.1.1/lib/net40/FSharp.Management.PowerShell.dll"
#r "System.Management.Automation"
#r "Microsoft.Management.Infrastructure"

open FSharp.Management
open Microsoft.PowerShell

type PS = PowerShellProvider< PSSnapIns="WDeploySnapin3.0", Is64BitRequired=false>
PowerShellProvider.Runtime

PS.``Set-ExecutionPolicy``(executionPolicy=ExecutionPolicy.RemoteSigned) 
PS.``Import-Module``(name=[|"Azure"|])

Some initialization...

// Ideal execution which doesn't seem to work
PS.``Add-AzureAccount``(  some params ... )

See "http://azure.microsoft.com/en-us/documentation/articles/install-configure-powershell/"
for more examples

How do I run commands from the Azure module?

In my opinion this would be an awesome feature for F# I think because it would open up many possibilities.

Regards
Stuart Davies

[dsyme]

Ping @forki @vasily-kirichenko @sergey-tihon @dtchepak We should answer this :)

@stuartjdavies - did you find a solution for this?

[vasily-kirichenko]

Sorry, I try To stay away from both PS and Azure.

[sergey-tihon]

@stuartjdavies sorry, i missed this question.

As I understand, it is not possible right now.
In order to get intellisense over Azure commands TP should load it before type inference.
So, it sounds like we should add new parameter to PowershellProvider.

[stuartjdavies]

@dsyme @forki @vasily-kirichenko @sergey-tihon

No, I didn't find a solution. It was a while since I looked at this but by memory I don't think it works for any package you want to load. Not just the azure package. If this is the case it might be a good feature to add. Anyway, there may better things to spend time on.

[ChristopherBuller]

I worked thru creating this exact feature before, The module cmdlets don't list with RunspaceConfiguration.Cmdlets so they are missing. A module cmdlet list can be piped into PSRuntimeHosted instance in the cmdlets member to fix the missing cmdlets.

I think I created an new constructor PSRuntimeHosted(snapIns:string[], modules:[])

I forget where I got stuck but the root issue is RunspaceConfiguration.Cmdlets don't list the module commands so they have to be added to the provider with additional effort.
***Edit
Actually now that I sent this message I remember where the conflict lives:
An easy path would be to configure the InitialSessionState but a runspace can be constructed with either a RunspaceConfig or an InitialSessionState. So I hacked it in by merging the runspace cmdlets from 2 runspaces, first being the original with configuration and another that gets created with initialsessionstate

[sergey-tihon]

Please try latest package from NuGet

type PS = PowerShellProvider< "Azure" >

[sergey-tihon]

Please test it and reopen this issue if needed