Feature/calendar api session caching issues 162 163 #164
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
2.25.0
New-GoogleService
now caches Service objects created during the current session. This means that repeated calls will attempt to use an existing Service object from the cache if present, otherwise it will create the Service as usual.New-GoogleService
Verbose output. To cut down on verbose noisiness, the following verbose output is set:Building ServiceAccountCredential from....
Using matching cached service for user....
Get-PSGSuiteServiceCache
to get the current Service Cache for inspection.Get-GSCalendar
to get the CalendarList of a user.Remove-GSCalendarAcl
to remove Access Control List rules from Google Calendars.*Message
functions and Calendar functions.Switch-PSGSuiteConfig
for the ConfigName parameter.