This blueprint creates a simple M4CE (v5) environment deployed on a single host project.
The blueprint is designed for quick tests or product demos where it is required to setup a simple and minimal M4CE (v5) environment. It also includes the IAM wiring needed to make such scenarios work.
This is the high level diagram:
This sample creates several distinct groups of resources:
- projects
- M4CE host project with required services deployed on a new or existing project.
- networking
- Default VPC network
- IAM
- One service account used at runtime by the M4CE connector for data replication
- Grant migration admin roles to admin user or group
- Grant migration viewer role to viewer user or group
| name | description | type | required | default |
|---|---|---|---|---|
| migration_admin | User or group who can create a new M4CE sources and perform all other migration operations, in IAM format (group:[email protected]). |
string |
✓ | |
| migration_viewer | User or group authorized to retrieve information about M4CE in the Google Cloud Console, in IAM format (group:[email protected]). |
string |
null |
|
| project_create | Parameters for the creation of the new project to host the M4CE backend. | object({…}) |
null |
|
| project_name | Name of an existing project or of the new project assigned as M4CE host an target project. | string |
"m4ce-host-project-000" |
|
| vpc_config | Parameters to create a simple VPC on the M4CE project. | object({…}) |
{…} |
| name | description | sensitive |
|---|---|---|
| m4ce_gmanaged_service_account | Google managed service account created automatically during the migrate connector registration. It is used by M4CE to perform activities on target projects. |
module "test" {
source = "./fabric/blueprints/cloud-operations/vm-migration/single-project"
project_create = {
billing_account_id = "1234-ABCD-1234"
parent = "folders/1234563"
}
migration_admin = "user:[email protected]"
migration_viewer = "user:[email protected]"
}
# tftest modules=5 resources=27