Context We are planning a Google Workspace migration and need to understand the potential impact on our existing Google Cloud projects that use the YouTube Data API v3.
Our Current Setup:
Workspace A: Manages the primary domain primary-domain.com and has its own Google Cloud Organization (Org A).
Workspace B: Manages the primary domain secondary-domain.com and has its own Google Cloud Organization (Org B).
A Google Cloud project within Org B actively uses the YouTube Data API v3. This project has configured credentials, including an OAuth 2.0 consent screen, OAuth Client IDs, and API Keys.
The Planned Migration Steps:
Our migration procedure has been revised as follows:
Domain Swap in Original Workspace: In Workspace B, we will swap the primary domain (secondary-domain.com) with a pre-added secondary domain (migration.secondary-domain.com). This action demotes secondary-domain.com to a secondary domain within its original workspace.
Domain Release and Re-add: We will then remove the secondary-domain.com domain from Workspace B, which releases it. Immediately afterward, we will add secondary-domain.com as a secondary domain to Workspace A.
After this process, the Google Cloud Organization (Org B) will remain where it is, but user identity will be managed by Workspace A.
API Keys: Our understanding is that API Keys are tied to the GCP project, not the Workspace. Can we assume that any server-side processes using an API Key to call the YouTube API will be unaffected?
Other Potential Issues: Are there any other potential impacts on the YouTube Data API v3 integration or other GCP services that we might be overlooking in this migration scenario?
