Releases: SCRT-HQ/PSGSuite
PSGSuite v2.22.2
Changelog
2.22.2
- Issue #144
- Updated:
Start-GSDriveFileUpload
toDispose()
open streams once uploads are completed. - Added:
Stop-GSDriveFileUpload
to enable cleanup of any remaining open streams. - Updated:
Get-GSDriveFileUpload
toDispose()
any completed streams that are still open.
- Updated:
Instructions
IMPORTANT: You MUST have the module 'Configuration' installed as a prerequisite! Installing the module from the repo source or the release page does not automatically install dependencies!!
- Click here to download the PSGSuite.zip file attached to the release.
- If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.
This is to prevent having to unblock each file individually after unzipping.
- Unzip the archive.
- (Optional) Place the module folder somewhere in your
PSModulePath
.You can view the paths listed by running the environment variable
$env:PSModulePath
- Import the module, using the full path to the PSD1 file in place of
PSGSuite
if the unzipped module folder is not in yourPSModulePath
:# In $env:PSModulePath Import-Module PSGSuite # Otherwise, provide the path to the manifest: Import-Module -Path C:\MyPSModules\PSGSuite\2.22.2\PSGSuite.psd1
PSGSuite v2.22.1
Changelog
Instructions
IMPORTANT: You MUST have the module 'Configuration' installed as a prerequisite! Installing the module from the repo source or the release page does not automatically install dependencies!!
- Click here to download the PSGSuite.zip file attached to the release.
- If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.
This is to prevent having to unblock each file individually after unzipping.
- Unzip the archive.
- (Optional) Place the module folder somewhere in your
PSModulePath
.You can view the paths listed by running the environment variable
$env:PSModulePath
- Import the module, using the full path to the PSD1 file in place of
PSGSuite
if the unzipped module folder is not in yourPSModulePath
:# In $env:PSModulePath Import-Module PSGSuite # Otherwise, provide the path to the manifest: Import-Module -Path C:\MyPSModules\PSGSuite\2.22.1\PSGSuite.psd1
PSGSuite v2.22.0
Changelog
2.22.0
- Miscellaneous: Config management and portability updates
- Added:
Export-PSGSuiteConfig
function to export key parts of your config in a transportable JSON file. - Added:
Import-PSGSuiteConfig
function to import a config from a JSON file (i.e. one created withExport-PSGSuiteConfig
) or from a JSON string (i.e. stored in a secure variable in a CI/CD system.) - Updated: All config functions now store the P12Key or the ClientSecrets JSON string in the encrypted config directly. This is to allow removal of the secrets files as well as enable PSGSuite to run in a contained environment via importing the config from a secure JSON string.
- Updated:
[Get|Set|Switch]-PSGSuiteConfig
to include the P12Key and ClientSecrets parameters that enable housing of the key/secret directly on the encrypted config. - Updated: If the global PSGSuite variable
$global:PSGSuite
exists during module import, it will default to using that as it's configuration, otherwise it will import the default config if set.
- Added:
Instructions
IMPORTANT: You MUST have the module 'Configuration' installed as a prerequisite! Installing the module from the repo source or the release page does not automatically install dependencies!!
- Click here to download the PSGSuite.zip file attached to the release.
- If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.
This is to prevent having to unblock each file individually after unzipping.
- Unzip the archive.
- (Optional) Place the module folder somewhere in your
PSModulePath
.You can view the paths listed by running the environment variable
$env:PSModulePath
- Import the module, using the full path to the PSD1 file in place of
PSGSuite
if the unzipped module folder is not in yourPSModulePath
:# In $env:PSModulePath Import-Module PSGSuite # Otherwise, provide the path to the manifest: Import-Module -Path C:\MyPSModules\PSGSuite\2.22.0\PSGSuite.psd1
PSGSuite v2.21.3
Changelog
2.21.3
- Issue #131
- Fixed: Changed
CodeReceiver
to usePromptCodeReceiver
when client is PowerShell Core, asLocalServerCodeReceiver
does not appear to redirect correctly and auth fails. Same behavior in Core regardless of OS.
- Fixed: Changed
- Miscellaneous
- Added:
OutputType
to all functions that return standard objects.
- Added:
Instructions
IMPORTANT: You MUST have the module 'Configuration' installed as a prerequisite! Installing the module from the repo source or the release page does not automatically install dependencies!!
- Click here to download the PSGSuite.zip file attached to the release.
- If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.
This is to prevent having to unblock each file individually after unzipping.
- Unzip the archive.
- (Optional) Place the module folder somewhere in your
PSModulePath
.You can view the paths listed by running the environment variable
$env:PSModulePath
- Import the module, using the full path to the PSD1 file in place of
PSGSuite
if the unzipped module folder is not in yourPSModulePath
:# In $env:PSModulePath Import-Module PSGSuite # Otherwise, provide the path to the manifest: Import-Module -Path C:\MyPSModules\PSGSuite\2.21.3\PSGSuite.psd1
PSGSuite v2.21.2
Changelog
2.21.2
- Issue #136
- Fixed:
Start-GSDriveFileUpload
failing when specifying a user other than the Admin user to do the upload as.
- Fixed:
Instructions
IMPORTANT: You MUST have the module 'Configuration' installed as a prerequisite! Installing the module from the repo source or the release page does not automatically install dependencies!!
- Click here to download the PSGSuite.zip file attached to the release.
- If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.
This is to prevent having to unblock each file individually after unzipping.
- Unzip the archive.
- (Optional) Place the module folder somewhere in your
PSModulePath
.You can view the paths listed by running the environment variable
$env:PSModulePath
- Import the module, using the full path to the PSD1 file in place of
PSGSuite
if the unzipped module folder is not in yourPSModulePath
:# In $env:PSModulePath Import-Module PSGSuite # Otherwise, provide the path to the manifest: Import-Module -Path C:\MyPSModules\PSGSuite\2.21.2\PSGSuite.psd1
PSGSuite v2.21.1
Changelog
2.21.1
- Issue #131 - Free/standard Google Account support
- Fixed: Handling of scopes in
New-GoogleService
for authentication when a client_secrets.json file is used instead of the typical .p12 key. - Updated: Documentation to show how to use an account that is not a G Suite admin or G Suite user at all with PSGSuite
- Updated:
*-PSGSuiteConfig
commands now store the client_secrets.json string contents directly on the encrypted config once provided either the path or the string contents directly, allowing users to remove any plain text credentials once loaded into the encrypted config. - Updated:
Get-GSToken
now usesNew-GoogleService
under the hood, soclient_secrets.json
will work with Contacts API.
- Fixed: Handling of scopes in
Instructions
IMPORTANT: You MUST have the module 'Configuration' installed as a prerequisite! Installing the module from the repo source or the release page does not automatically install dependencies!!
- Click here to download the PSGSuite.zip file attached to the release.
- If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.
This is to prevent having to unblock each file individually after unzipping.
- Unzip the archive.
- (Optional) Place the module folder somewhere in your
PSModulePath
.You can view the paths listed by running the environment variable
$env:PSModulePath
- Import the module, using the full path to the PSD1 file in place of
PSGSuite
if the unzipped module folder is not in yourPSModulePath
:# In $env:PSModulePath Import-Module PSGSuite # Otherwise, provide the path to the manifest: Import-Module -Path C:\MyPSModules\PSGSuite\2.21.1\PSGSuite.psd1
PSGSuite v2.21.0
Changelog
2.21.0
- PR #130 / Issue #129
- Added: Support for UserRelations management in
New-GSUser -Relations $relations
andUpdate-GSUser -Relations $relations
viaAdd-GSUserRelation
helper function. - Thanks, @mattwoolnough! - Added: Logic to
Update-GSUser
to enable clearing of all values for user propertiesPhones
,ExternalIds
,Organizations
, andRelations
by REST API call via passing$null
as the value when callingUpdate-GSUser
. - Thanks, @mattwoolnough!
- Added: Support for UserRelations management in
- Issue #129
- Fixed: Documentation for
Get-GSSheetInfo
around theFields
parameter. - Added: Additional correction of casing for
Fields
values inGet-GSSheetInfo
so that it will always submit the values using the correct case, even if providing the incorrect case as the value to the parameter.
- Fixed: Documentation for
Instructions
IMPORTANT: You MUST have the module 'Configuration' installed as a prerequisite! Installing the module from the repo source or the release page does not automatically install dependencies!!
- Click here to download the PSGSuite.zip file attached to the release.
- If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.
This is to prevent having to unblock each file individually after unzipping.
- Unzip the archive.
- (Optional) Place the module folder somewhere in your
PSModulePath
.You can view the paths listed by running the environment variable
$env:PSModulePath
- Import the module, using the full path to the PSD1 file in place of
PSGSuite
if the unzipped module folder is not in yourPSModulePath
:# In $env:PSModulePath Import-Module PSGSuite # Otherwise, provide the path to the manifest: Import-Module -Path C:\MyPSModules\PSGSuite\2.21.0\PSGSuite.psd1
PSGSuite v2.20.2
Changelog
2.20.2
- Issue #120
- Added:
Update-GSMobileDevice
to allow taking action on Mobile Devices - Fixed: Bug in
Remove-GSMobileDevice
with incorrect variable name
- Added:
Instructions
IMPORTANT: You MUST have the module 'Configuration' installed as a prerequisite! Installing the module from the repo source or the release page does not automatically install dependencies!!
- Click here to download the PSGSuite.zip file attached to the release.
- If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.
This is to prevent having to unblock each file individually after unzipping.
- Unzip the archive.
- (Optional) Place the module folder somewhere in your
PSModulePath
.You can view the paths listed by running the environment variable
$env:PSModulePath
- Import the module, using the full path to the PSD1 file in place of
PSGSuite
if the unzipped module folder is not in yourPSModulePath
:# In $env:PSModulePath Import-Module PSGSuite # Otherwise, provide the path to the manifest: Import-Module -Path C:\PSGSuite\2.20.2\PSGSuite.psd1
PSGSuite v2.20.1
Changelog
2.20.1
- Issue #121
- Added:
Update-GSGroupMember
to allow setting a group member's Role and/or DeliverySettings
- Added:
- Miscellaneous
- Added: GitHub release automation to deploy task
- Added: Twitter update automation on new version release to deploy task
Instructions
IMPORTANT: You MUST have the module 'Configuration' installed as a prerequisite! Installing the module from the repo source or the release page does not automatically install dependencies!!
- Click here to download the PSGSuite.zip file attached to the release.
- If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.
This is to prevent having to unblock each file individually after unzipping.
- Unzip the archive.
- (Optional) Place the module folder somewhere in your
PSModulePath
.You can view the paths listed by running the environment variable
$env:PSModulePath
- Import the module, using the full path to the PSD1 file in place of
PSGSuite
if the unzipped module folder is not in yourPSModulePath
:# In $env:PSModulePath Import-Module PSGSuite # Otherwise, provide the path to the manifest: Import-Module -Path C:\PSGSuite\2.20.1\PSGSuite.psd1
PSGSuite v2.20.0
Changelog
2.20.0
- Issue #115
- Renamed:
Get-GSCalendarEventList
toGet-GSCalendarEvent
and set the original name as an exported Alias to the new name for backwards compatibility. - Added:
EventId
parameter toGet-GSCalendarEvent
to specify individual event ID's to get instead of a filtered list. - Added:
PrivateExtendedProperty
parameter toGet-GSCalendarEvent
. - Added:
SharedExtendedProperty
parameter toGet-GSCalendarEvent
. - Added:
PrivateExtendedProperties
parameter toNew-GSCalendarEvent
andUpdate-GSCalendarEvent
. - Added:
SharedExtendedProperties
parameter toNew-GSCalendarEvent
andUpdate-GSCalendarEvent
. - Added:
ExtendedProperties
parameter toNew-GSCalendarEvent
andUpdate-GSCalendarEvent
. - Added:
Id
parameter toNew-GSCalendarEvent
andUpdate-GSCalendarEvent
.
- Renamed:
- Issue #117
- Fixed: Type error on
States
parameter ofGet-GSStudentGuardianInvitation
.
- Fixed: Type error on
- Miscellaneous
- Updated Contributing doc with new Build script steps
- Removed
DebugMode.ps1
script since it's no longer needed (usebuild.ps1
instead)
Instructions
IMPORTANT: You MUST have the module 'Configuration' installed as a prerequisite! Installing the module from the repo source or the release page does not automatically install dependencies!!
- Click here to download the PSGSuite.zip file attached to the release.
- If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.
This is to prevent having to unblock each file individually after unzipping.
- Unzip the archive.
- (Optional) Place the module folder somewhere in your
PSModulePath
.You can view the paths listed by running the environment variable
$env:PSModulePath
- Import the module, using the full path to the PSD1 file in place of
PSGSuite
if the unzipped module folder is not in yourPSModulePath
:# In $env:PSModulePath Import-Module PSGSuite # Otherwise, provide the path to the manifest: Import-Module -Path C:\PSGSuite\2.20.0\PSGSuite.psd1