Add support for Database Migration Service Conversion Workspace resource

[naseemsm]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment
• If an issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to "hashibot", a community member has claimed the issue already.

Description

The Database Migration Service API supports Conversion Workspaces, which are used to convert databases from one engine to another (e.g., Oracle to PostgreSQL, MySQL to PostgreSQL, SQL Server to PostgreSQL). However, there is currently no Terraform resource to manage these conversion workspaces.

New or Affected Resource(s)

• google_database_migration_service_conversion_workspace (NEW)

Potential Terraform Configuration

resource "google_database_migration_service_conversion_workspace" "example" {
  location                = "us-central1"
  conversion_workspace_id = "my-conversion-workspace"
  display_name           = "My conversion workspace"
  
  source {
    engine  = "ORACLE"
    version = "21c"
  }
  
  destination {
    engine  = "POSTGRESQL"
    version = "15"
  }
  
  global_settings = {
    "skip_triggers"      = "false"
    "max_parallel_level" = "5"
  }
}

API Documentation

• Conversion Workspace API Reference
• Database Engine Types

Use Case

Organizations migrating databases between different engines need to:

1. Create conversion workspaces to manage the schema and data conversion process
2. Configure source and destination database engines
3. Apply conversion settings for specific migration requirements
4. Track conversion progress and manage the conversion lifecycle

Currently, users must use the gcloud CLI or Cloud Console to manage conversion workspaces, which breaks Infrastructure as Code workflows.

Supported Conversions

Based on API testing, the following conversions are supported:

• Oracle → PostgreSQL
• MySQL → PostgreSQL
• SQL Server → PostgreSQL

References

• gcloud command: gcloud database-migration conversion-workspaces create