Developer Connect complies with data residency requirements. Data residency describes where your data is stored at rest. To ensure compliance, Developer Connect does the following:
- stores resource data in regional Spanner instances
- replicates data only within designated cloud regions
- queues webhook data within regional Spanner queues
However, this isn't true for all connections. By default, GitHub connections use a global Pub/Sub topic for event delivery. The topic is then replicated to regional subscriptions. Although the Pub/Sub messages aren't stored permanently by Pub/Sub, this global routing doesn't meet data residency requirements because Pub/Sub stores each message in a global topic temporarily.
When you create a GitHub connection using Google Cloud CLI, that connection is regional, but the Developer Connect GitHub app that the connection uses is global, and thefore doesn't comply with data residency requirements.
When you create a GitHub connection using Google Cloud console, data residency is disabled by default for that connection. You can enable it by activating the Enable data residency checkbox. Doing so makes this GitHub connection data-residency compliant. Developer Connect creates a GitHub app for your connection, owned by your GitHub user account or organization. The app uses a per-connection, regionalized webhook endpoint.
To create a data-residency compliant GitHub connection, see
Connect to GitHub.