Understand how customers see your app's deployment packages

If you offer Terraform Kubernetes apps through Google Cloud Marketplace which are based on auto-generated standard packages, your customers see the following screen layouts when they get your product and deploy it.

Customer view of deploying a package

Terraform UI

The standard customer input elements are shown on the left side of the following screenshot and include zone, machine type, disk options, and networking options. If your product supports Terraform UI deployment, your customers can switch between Terraform UI or Terraform CLI.

The customer must specify a deployment service account, which Infra Manager uses to run the command Terraform apply.

If a customer's deployment requires multiple network interface cards, they can add additional network interfaces by clicking Add network interface.

To deploy your product, your customers must fill out the input fields, and then click Deploy.

Terraform CLI

The following screenshot shows the standard customer input elements, which include the following:

  • Service account
  • gcloud CLI configuration instructions

To deploy your product, your customer must do the following:

  • Copy the provided command.
  • Replace any placeholders, such as deployment name and service account.

If your Terraform module requires inputs that don't have a default value, you must describe these inputs in the user guide that you provide to your customers.

Customer view of a deployed package

The following screenshot shows how your product appears to customers after they've successfully deployed it. This includes the following standard output elements:

  • Site address
  • Temporary administrator password
  • Instance information

If a deployment fails, customers can click View logs to be redirected to the logs of the Cloud Build job that actuated the Terraform configuration.