Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data Transfer calendar release ressources #213

Closed
ABricka opened this issue Jul 24, 2019 · 5 comments
Closed

Data Transfer calendar release ressources #213

ABricka opened this issue Jul 24, 2019 · 5 comments
Assignees

Comments

@ABricka
Copy link

ABricka commented Jul 24, 2019

Hi @scrthq , i can't find any solution to your Start-GSDataTransfer command for apply the release_ressource parameter.
I imagine is possible cause "GAM" do it but I don't want to use gam only for this so if you got any hidden feature or whatever to do it I'll be very happy :)

For "help" there is the gam command in first and my command in 2nd i want to implement the release ressource :

gam create datatransfer oldguy@acme.com calendar newguy@acme.com release_resources true

Start-GSDataTransfer -OldOwnerUserId $username -NewOwnerUserId $Ownershipuname -ApplicationID 435XXXXXXXXX -PrivacyLevel SHARED

Alex

@scrthq
Copy link
Member

scrthq commented Jul 24, 2019

Hey @ABricka - It looks like that Start-GSDataTransfer needs to be updated to support it! Privacy_Level is Drive and Docs specific, but I'm seeing the RELEASE_RESOURCES TransferParam on the Calendar DataTransferApplication specifically:

image

Considering this a feature request, I'll let you know once available!

@scrthq scrthq self-assigned this Jul 24, 2019
@ABricka
Copy link
Author

ABricka commented Jul 25, 2019

Super :) That's a great new !
Waiting about you to use it :)
Thanks a lot for this fast reaction 👍

scrthq added a commit that referenced this issue Jul 31, 2019
## 2.31.0

* [Issue #218](#218)
  * Fixed: Update-GSOrganizationalUnit was failing with
ull reference errors.
* [Issue #213](#213)
  * Added: Support for RELEASE_RESOURCES TransferParam for Calendar application data transfers to function Start-GSDataTransfer
* [Issue #215](#215)
  * Added:
    * Get-GSDomain
    * Remove-GSDomain
    * New-GSDomain
    * Get-GSDomainAlias
    * New-GSDomainAlias
    * Remove-GSDomainAlias
  * _These will need the additional scope of https://www.googleapis.com/auth/admin.directory.domain added in order to use!_
* Miscellaneous
  * Added:
    * Get-GSCustomer
    * Update-GSCustomer
    * Add-GSCustomerPostalAddress
  * _These will need the additional scope of https://www.googleapis.com/auth/admin.directory.customer added in order to use!_
scrthq added a commit that referenced this issue Jul 31, 2019
## 2.31.0

* [Issue #218](#218)
  * Fixed: `Update-GSOrganizationalUnit` was failing with `null` reference errors.
* [Issue #213](#213)
  * Added: Support for `RELEASE_RESOURCES` TransferParam for Calendar application data transfers to function `Start-GSDataTransfer`
* [Issue #215](#215)
  * Added:
    * `Get-GSDomain`
    * `Remove-GSDomain`
    * `New-GSDomain`
    * `Get-GSDomainAlias`
    * `New-GSDomainAlias`
    * `Remove-GSDomainAlias`
  * _These will need the additional scope of `https://www.googleapis.com/auth/admin.directory.domain` added in order to use!_
* Miscellaneous
  * Added:
    * `Get-GSCustomer`
    * `Update-GSCustomer`
    * `Add-GSCustomerPostalAddress`
  * _These will need the additional scope of `https://www.googleapis.com/auth/admin.directory.customer` added in order to use!_
@scrthq
Copy link
Member

scrthq commented Jul 31, 2019

Hey @ABricka - added support for this in 2.31.0! Usage (note that ReleaseResources is a [Switch] parameter, so no need to pass $true):

$calendarApp = Get-GSDataTransferApplication | Where-Object {$_.Name -eq 'Calendar'}
Start-GSDataTransfer -OldOwnerUserId $username -NewOwnerUserId $Ownershipuname -ApplicationID $calendarApp.Id -ReleaseResources

@scrthq scrthq closed this as completed Jul 31, 2019
@ABricka
Copy link
Author

ABricka commented Jul 31, 2019

Super, thanks a lot 👍

@scrthq
Copy link
Member

scrthq commented Jul 31, 2019

You bet!

Sent with GitHawk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants