guitarrapc_tech

My feedback

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

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    guitarrapc_tech commented  · 

    May be better shift to xService in xPSDesiredStateConfiguration Resource. https://github.com/PowerShell/xPSDesiredStateConfiguration

  2. 36 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    guitarrapc_tech supported this idea  · 
  3. 6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    survey  ·  1 comment  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    guitarrapc_tech supported this idea  · 
  4. 12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    guitarrapc_tech supported this idea  · 
    An error occurred while saving the comment
    guitarrapc_tech commented  · 

    It's not partial Configuration but I have same symptom with WMF5 RTM.

    When LCM Set as following, then run Update-DscConfiguration often failed with;

    The specified Property does not exist.
    + CategoryInfo : MetadataError: (root/Microsoft/...;gurationManager:String) [], CimException
    + FullyQualifiedErrorId : MI RESULT 12
    + PSComputerName : localhost

    There's LCM Configuration I've test.

    ```
    [DSCLocalConfigurationManager()]
    configuration LCMPullClient
    {
    Node localhost
    {
    Settings
    {
    RefreshMode = "Pull"
    ConfigurationModeFrequencyMins = 15
    RefreshFrequencyMins = 30
    RebootNodeIfNeeded = $false
    ConfigurationMode = "ApplyAndAutoCorrect"
    ActionAfterReboot = "ContinueConfiguration"
    AllowModuleOverwrite = $true
    }

    ConfigurationRepositoryWeb PullServer
    {
    ServerURL = "http://DSCServer:8080/PSDSCPullServer.svc"
    RegistrationKey = "GUID FOR KEY"
    ConfigurationNames = "PullClient"
    AllowUnsecureConnection = $true
    }

    ResourceRepositoryWeb PullServer
    {
    ServerURL = "http://DSCServer:8080/PSDSCPullServer.svc"
    RegistrationKey = "GUID FOR KEY"
    AllowUnsecureConnection = $true
    }

    ReportServerWeb PullServer
    {
    ServerURL = "http://DSCServer:8080/PSDSCPullServer.svc"
    RegistrationKey = "GUID FOR KEY"
    AllowUnsecureConnection = $true
    }
    }
    }
    ```

  5. 59 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    guitarrapc_tech supported this idea  · 
  6. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    guitarrapc_tech commented  · 

    PowerShell Hashtable create with IEquialityComparer Constructor. Thus you can avoid with passing StringComparer.CurrentCultureIgnoreCase.

    An error occurred while saving the comment
    guitarrapc_tech commented  · 

    Understand PowerShell @{} is not equivalent with new Hashtable() but it create with IEqualityComparer.

    Following C# Hashtable will work as much like PowerShell Hashtable, not same but quite near and can be use for DSC ConfigurationData in C#.

    >>>>
    private static readonly StringComparer _comparer = StringComparer.CurrentCultureIgnoreCase;

    ConfigurationData = new Dictionary<string, Hashtable[]>
    {
    {
    "AllNodes", new [] {
    new Hashtable(_comparer)
    {
    // *
    { "NodeName", "*" },
    { "PSDscAllowPlainTextPassword", true },
    },
    // All localhost
    new Hashtable(_comparer)
    {
    { "NodeName", "localhost"},
    }
    }
    },
    };
    >>>>

    Also in PowerShell v5 like this.

    >>>>
    class HashtableComparer : System.Collections.IEqualityComparer
    {
    [bool] Equals([object]$obj, [object]$obj2)
    {
    return $obj -eq $obj2;
    }

    [int] GetHashCode([object]$obj)
    {
    return $obj.ToString().ToLower().GetHashCode();
    }
    }
    $comparer = New-Object HashtableComparer;

    # sample configuration
    configuration Hoge
    {
    Node localhost
    {
    File Hoge
    {
    Ensure = $Node.Ensure
    DestinationPath = $Node.DestinationPath
    Type = 'Directory'
    }

    User Hoge
    {
    UserName = "Hoge"
    Password = $Node.Credential
    Ensure = 'Present'
    Disabled = $false
    }
    }
    }

    $cred = (Get-Credential)

    # create configurationData
    $configurationData = New-Object 'System.Collections.Generic.Dictionary[string, hashtable[]]'
    $a = New-Object System.Collections.Hashtable ($comparer)
    $a.Add("Credential",$cred)
    $a.Add("NodeName", "*")
    $a.Add("PSDSCAllowPlainTextPassword", $true)
    $a.Add("Ensure", "Present")
    $a.Add("DestinationPath","c:\fuga")

    $b = New-Object System.Collections.Hashtable ($comparer)
    $b.Add("NodeName","localhost")

    $configurationData["AllNodes"] = @($a, $b)

    Hoge -ConfigurationData $configurationData
    Start-DscConfiguration -Wait -Force -Verbose Hoge
    >>>>

    An error occurred while saving the comment
    guitarrapc_tech commented  · 
    guitarrapc_tech shared this idea  · 
  7. 4 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 » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    guitarrapc_tech commented  · 

    As this functionality is impremented in https://github.com/PowerShell/xPSDesiredStateConfiguration, it would be nice back ported to Standard Service Resource.

    guitarrapc_tech supported this idea  · 
  8. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » Desired State Configuration (DSC)  ·  Flag idea as inappropriate…  ·  Admin →
    guitarrapc_tech supported this idea  · 
  9. 17 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Any update with? I have this issue long time with WMF 5 and also other users experience same issues. https://github.com/guitarrapc/DSCResources/issues/58

    guitarrapc_tech supported this idea  · 
  10. 56 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    survey  ·  Zachary Alexander responded

    Thank you for your input. Based on its current ranking compared to other feedback items and product schedule, work on this item is pending (and will be driven by) further customer input.

    An error occurred while saving the comment
    guitarrapc_tech commented  · 

    Imagine like you need to compile multiple platform target for same project. It's messy creating Start-CompileiOSBuild, Start-CompileAndroidBuild, Start-CompileWindowsSupport...

    Compile verb will let you name as Compile-AndroidBuild, Compile-iOSBuild and so on. Name what you want exactly is what PowerShell stands and it might be much for Cross Platform DevOps.

    guitarrapc_tech supported this idea  · 
  11. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PowerShell » Package Management  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    guitarrapc_tech commented  · 

    This is actually very important for both developer and user to recognize license. As NuGet.org do, license is mandatory for all developers who want to publish it.

    Let's think about MIT and GNU v3, did PowerShell core import PSReadline and Pester if license are GNU? I don't think so.

    I hope PS Gallery will show License URL in each pages, and would be prefer if License can be written in .psd1 or mandatory when publishing module with Publish-Module.

    guitarrapc_tech supported this idea  · 
  12. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    guitarrapc_tech supported this idea  · 
  13. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    guitarrapc_tech supported this idea  · 
  14. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    guitarrapc_tech supported this idea  · 
  15. 10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PowerShell » Microsoft.PowerShell.* Modules  ·  Flag idea as inappropriate…  ·  Admin →
    guitarrapc_tech supported this idea  · 
  16. 20 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 » PowerShell Engine  ·  Flag idea as inappropriate…  ·  Admin →
    guitarrapc_tech supported this idea  · 
  17. 0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    guitarrapc_tech commented  · 

    You should use @psd1 for splatting. $psd1 doesn't recognize as Splatting.

Feedback and Knowledge Base