In GCP, a Landing Zone is defined via folder the project will be assigned to. Policies can be applied to these folders.
The Landing Zone can be configured in the
Administration section. If a project is selected to have an GCP location a Landing Zone must be selected by the user. By choosing a landing zone, platform specific configuration can be set (in this case for GCP). The options for GCP are:
Folders and the application of organization constrains on the projects contained in them through the use of Organization Policy Service can be setup outside of meshcloud by an Operator.
Cloud Function URL
If you specify a Cloud Function URL this function will get invoked during a project replication. This can happen several times and thus your function invocation must be idempotent. The function gets variables provided via HTTP headers similar to the Azure Function.
Please make sure the GCP service user of the replicator is allowed to access this function.
The following HTTP headers are provided to the Cloud Function:
|HTTP Header Name||Description|
|x-mesh-costcenter||ID of the CostCenter defined for this meshProject.|
|x-mesh-project-identifier||The project identifier|
|x-mesh-project-id||The ID of the GCP project associated with this meshProject|
In addition, any payment settings, project tags or customer tags are also provided to the Cloud Function, after formatting the tag name to an http header name. For example, a tag named myCustomerTag would be provided as an HTTP header with name x-mesh-tag-my-customer-tag.