Koans/Cmdlets 1/AboutPSProviders.Koans.ps1
|
#Requires -Module PSKoans [Koan(202)] param() <# PSProviders Providers are PowerShell's general-purpose solution for accessing resources. The default set of providers that come with PowerShell on all platforms are listed below: Name Capabilities Drives ---- ------------ ------ Alias ShouldProcess {Alias} Environment ShouldProcess {Env} FileSystem Filter, ShouldProcess, Credentials {/} Function ShouldProcess {Function} Variable ShouldProcess {Variable} Several are for accessing internal PowerShell resources (aliases, functions, variables), but the rest typically interact with the surrounding environment like the filesystem or OS environment. On Windows, PowerShell also comes with a Registry provider, for interacting with the Windows registry. All providers that have a defined function with the Get-Content cmdlet can also be accessed similarly to variable scopes, e.g., { $env:Path } instead of { Get-Content 'Env:Path' } #> Describe 'Alias Provider' { <# Aliases are PowerShell command shortcuts. By querying the Alias: provider, you can get a list of all command shortcuts in the current session. The available aliases may increase when a new module is imported. #> Context 'Direct Access' { It 'can be queried with generic provider cmdlets' { $Aliases = Get-ChildItem 'Alias:' $Aliases.Count | Should -Be __ $Aliases.Name[0] | Should -Be __ $Aliases.Definition[0] | Should -Be __ } It 'maps aliases to the full command' { $Alias = '__' $AliasObject = Get-Item "Alias:\$Alias" -ErrorAction SilentlyContinue $AliasObject | Get-Content | Should -Be 'Set-Location' } It 'can create aliases too!' { New-Item -Path 'Alias:\grok' -Value 'Get-Item' -ErrorAction SilentlyContinue $File = grok '__' -ErrorAction SilentlyContinue $File | Should -BeOfType 'System.IO.FileInfo' } } Context 'Access Via Cmdlet' { It 'can be accessed with Get-Alias' { $AliasObjects = Get-ChildItem 'Alias:' $AliasObjects2 = Get-Alias $AliasObjects2.Count | Should -Be __ $AliasObjects | Should -Be $AliasObjects2 } It 'allows for seeking out aliases for a command' { $CmdletName = __ $AliasData = Get-Alias -Definition $CmdletName $AliasData.Name | Should -Be 'gcm' } It 'can be used to find the exact command' { $AliasData = Get-Alias -Name 'ft' $AliasData.Definition | Should -Be '__' } It 'can create aliases too!' { Set-Alias -Name 'grok' -Value 'Get-Item' $File = grok $home $File | Should -BeOfType __ } } Context 'Variable Access' { It 'can be accessed like a variable' { $Alias:gci | Should -Be __ } It 'is the same as using Get-Content on the path' { Get-Content -Path 'Alias:\gcm' | Should -Be $Alias:gcm Get-Content -Path 'Alias:\echo' | Should -Be __ } } } Describe 'Environment Provider' { <# The Env: drive contains system environment data. Its contents can vary wildly from OS to OS, especially between Windows, Mac, and Linux, for example. The only shared Env: items across all OS's currently are Path and PSModulePath. #> $EnvironmentData = Get-ChildItem -Path 'Env:' It 'allows access to system environment data' { $SelectedItem = $EnvironmentData.Where{ $_.Value -is [string] }[7] $SelectedItem | Get-Content | Should -Be '__' $SelectedItem.Name | Should -Be '__' } It 'can be accessed via variables' { $env:Path | Should -Be '__' } } Describe 'FileSystem Provider' { $Path = $home | Join-Path -ChildPath 'File001.tmp' if (-not (Test-Path $Path)) { New-Item -Path $Path > $null -join (1..10000 | ForEach-Object { Get-Random -Minimum 32 -Maximum 96 | ForEach-Object {[char]$_ -as [string]} if ((Get-Random) -match '[25]0$') { "`n" } }) | Set-Content -Path $Path } It 'allows access to various files and their properties' { $File = Get-Item -Path $Path $File.Name | Should -Be '__' $File.Attributes | Should -Be '__' $File.Length | Should -Be '__' } It 'allows you to extract the contents of files' { $FirstLine = Get-Content -Path $Path | Select-Object -First 1 $FirstLine | Should -Be '__' } It 'allows you to copy, rename, or delete files' { $File = Get-Item -Path $Path $NewPath = "$Path-002" $NewFile = Copy-Item -Path $Path -Destination $NewPath -PassThru $NewFile.Length | Should -Be $File.Length $NewFile.Name | Should -Be '__' $NewFile = Rename-Item -Path $NewPath -NewName 'TESTNAME.tmp' -PassThru $NewFile.Name | Should -Be '__' $NewFile.Length | Should -Be '__' $FilePath = $NewFile.FullName Remove-Item -Path $FilePath {Get-Item -Path $FilePath -ErrorAction Stop} | Should -Throw -ExceptionType '__' } } Describe 'Function Provider' { $Functions = Get-ChildItem 'Function:' It 'allows access to all currently loaded functions' { # Most proper functions are named in the Verb-Noun convention $Functions[5].Verb | Should -Be '__' $Functions[5].Noun | Should -Be '__' $Functions[5].Name | Should -Be '__' $Functions[4].Name | Should -Be '__' } It 'exposes the entire script block of a function' { $Functions[3].ScriptBlock | Should -BeOfType ScriptBlock $Functions[1].ScriptBlock.ToString().Length | Should -Be __ $Functions[4] | Get-Content | Should -BeOfType __ } It 'allows you to rename the functions however you wish' { function Test-Function {'Hello!'} $TestItem = Get-Item 'Function:\Test-Function' Test-Function | Should -Be 'Hello!' $TestItem | Rename-Item -NewName 'Get-Greeting' Get-Greeting | Should -Be '__' } It 'can also be accessed via variables' { function Test-Function {'Bye!'} <# Because most functions use hyphens, their names are atypical for variables, and the ${} syntax must be used to indicate to the PowerShell parser that all contained characters are part of the variable name. #> ${function:Test-Function} | Should -BeOfType __ } It 'can be defined using variable syntax' { <# Although slower than the usual method of creating functions, it is a quick way to make a function out of a script block. #> $Script = { 1..3 } ${function:Get-Numbers} = $Script Get-Numbers | Should -Be __ } } Describe 'Variable Provider' { <# The variable provider allows direct access to variables as objects, allowing you to determine the name, value, and metadata of variables that are available in the current session and scope. #> Context 'Generic Cmdlets' { It 'allows access to variables in the current scope' { Set-Variable -Name 'Test' -Value 22 $VariableData = Get-Item 'Variable:\Test' $VariableData.Name | Should -Be 'Test' $VariableData.Value | Should -Be __ $VariableData.Options | Should -Be __ } It 'allows you to remove variables' { $Test = 123 $Test | Should -Be __ Remove-Item 'Variable:\Test' $Test | Should -Be __ {Get-Item 'Variable:\Test'} | Should -Throw -ExceptionType __ } It 'exposes data from default variables' { $Variables = Get-ChildItem 'Variable:' $Variables.Where{$_.Name -eq 'ConfirmPreference'}.Value | Should -Be __ $Variables.Where{$_.Name -eq 'MaximumAliasCount'}.Value | Should -Be __ } It 'allows you to set variable options' { Set-Variable -Name 'Test' -Value 'TEST' $Var = Get-Item 'Variable:\Test' $Var.Options = [System.Management.Automation.ScopedItemOptions]::ReadOnly $Var | Should -Be __ {Remove-Item 'Variable:\Test'} | Should -Throw -ExceptionType __ } } Context 'Variable Cmdlets' { It 'works similarly to the generic cmdlets' { Set-Variable 'test' -Value 7357 $Info = Get-Variable -Name 'Test' $Info.Options | Should -Be __ $Info.Name | Should -Be 'test' $Info.Value | Should -Be __ } It 'can retrieve just the value' { Set-Variable 'GetMe' -Value 'GOT!' $Get = Get-Variable -Name 'GetMe' -ValueOnly $Get | Should -Be __ } } } |