Anonymous

My feedback

  1. 13 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    WORKAROUND: :-) I found a suitable workaround, which was to dynamically retrieve the value of the desired resource group name as a default parameter value for $resourceGroup in the New-AutomationConnectionAsset user defined function. I also deliberately reduced the string length to 19 characters by invoking the substring method. Please see the attached updated function and the result image. Dear PowerShell Team - please don't close this bug yet as it seems that there is still a problem with the native Cmdlet New-AzAutomationConnection and I would be interested to know when this is resolved (if possible). Thanks to everyone who upvoted my issue. :-)

    Anonymous shared this idea  · 
  2. 117 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →

    Hi everyone,

    With PowerShell 6.0, we’ve already begun updating our versioning system to be more descriptive. Right now, PSVersion returns 6.0.0-alpha as a System.Management.Automation.SemanticVersion object (with Major, Minor, Patch, and Label properties), and we’ve also added a GitCommitId property to PSVersionTable that matches perfectly with tags on GitHub: https://github.com/powershell/powershell/tags

    Still, we can definitely continue to improve the semantic version implementation. You can track (and contribute to!) the discussion on these improvements here: https://github.com/PowerShell/PowerShell/issues/2354

    Thanks,
    Joey

    Anonymous supported this idea  · 

Feedback and Knowledge Base