Provisioning Config

Each service can be deployed with a given provisioning configuration as per need. Below is how a provisioning config can be defined e.g. provisioning-dev.json

[
    {
        "component_name": "COMPONENT_1",
        "deployment_type": "container"
    },
    {
        "component_name": "COMPONENT_2",
        "deployment_type": "container"
    }
]

Provisioning for GCP based clusters

For provisioning on gcp based cluster

[
    {
        "component_name": "COMPONENT_1",
        "deployment_type": "gcp_container"
    },
    {
        "component_name": "COMPONENT_2",
        "deployment_type": "gcp_container"
    }
]

RESTRICTION for GCP

For a service, deployment types container and gcp_container can not be used together. We recognise this isn't ideal, and rest assured, we ensure that this will be feasible in the near future.

[
  {
    "component_name": "foo",
    "deployment_type": "gcp_container"
  },
  {
    "component_name": "bar",
    "deployment_type": "container"
  }
]

For the above configuration of provisioning file, you will get an error.

[
  {
    "component_name": "foo",
    "deployment_type": "gcp_container"
  },
  {
    "component_name": "bar",
    "deployment_type": "aws_ec2"
  }
]

For the above configuration of provisioning file, component foo will be deployed as a container on GKE Cluster, and component bar will be deployed as an EC2 on an AWS Account.

[
  {
    "component_name": "foo",
    "deployment_type": "container"
  },
  {
    "component_name": "bar",
    "deployment_type": "aws_ec2"
  }
]

For the above configuration of provisioning file, component foo will be deployed as a container on EKS Cluster, and component bar will be deployed as an EC2 on an AWS Account.