4 - Environment

Updated 1 month ago by Michael Cretzman

Environments represent one or more of your deployment infrastructures, such as Dev, QA, Stage, Production, etc. For Artifact Build and Deploy Pipelines, the Environment specifies the Service containing the new artifact for the Deploy Workflow to use and the target deployment infrastructure where the new build will be deployed.

To set up the Environment, do the following:

  1. In your Harness Application, click Environments, and then click Add Environment. The Environment dialog appears.

  2. In Name, enter a name for the Environment that identifies it to your colleagues. In our example, we use File-Based.
  3. In Environment Type, select Production or Non-Production, and click SUBMIT. The new Environment is added.

Next, we will add a Service Infrastructure/Infrastructure Definition to provide the Deploy Workflow with the target deployment environment.

Infrastructure Definition

Infrastructure Definitions are a feature-flagged replacement for Service Infrastructure.

​Infrastructure Definitions specify the target deployment infrastructure for your Harness Services, and the specific infrastructure details for the deployment, like VPC settings. 

For Artifact Build and Deploy Pipelines, you will scope the ​Infrastructure Definition to the Service you added earlier where you identified the Artifact Source for your artifact. You will also use the Cloud Provider you set up in Harness Account Setup to configure the ​Infrastructure Definition. Then you will specify the target infrastructure for the deployment. In our example, we use an AWS EC2 instance.

To set up the ​Infrastructure Definition, do the following:

  1. In the Environment, click Add ​Infrastructure Definition. The ​Infrastructure Definition dialog appears.
  2. In Display Name, enter a name for the Service Infrastructure. In our example, we use ToDo List WAR.
  3. In Cloud Provider Type, select the type of Cloud Provider you used in Harness Account Setup.
  4. In Deployment Type, select Secure Shell (SSH).
  5. Click Use Already Provisioned Infrastructure. If you were using a Harness Infrastructure Provisioner, you would select Map Dynamically Provisioned Infrastructure.
  6. In Cloud Provider, select the Cloud Provider you set up in Harness Account Setup.
  7. Fill out the remaining infrastructure settings for your target deployment infrastructure.
  8. In Scope to specific Services, select the Service you created in Service and Artifact Source.

Here is an example that targets an AWS EC2 instance:

Click SUBMIT. The Infrastructure Definition is added. You will select this Infrastructure Definition when you create the Deploy Workflow.

Service Infrastructure

Harness now uses Infrastructure Definitions (which are a feature-flagged replacement for Service Infrastructure).

Service Infrastructures specify a deployment infrastructure using a Service, a Cloud Provider, and the specific infrastructure details for the deployment, like VPC settings. 

For Artifact Build and Deploy Pipelines, you will specify the Service you added earlier where you identified the Artifact Source for your artifact, and the Cloud Provider you set up in Harness Account Setup. Then you will specify the target infrastructure for the deployment. In our example, we use an AWS EC2 instance.

To set up the Service Infrastructure, do the following:

  1. In the Environment, click Add Service Infrastructure. The Service Infrastructure dialog appears.
  2. In Display Name, enter a name for the Service Infrastructure. In our example, we use ToDo List WAR.
  3. In Service, select the Service you created in Service and Artifact Source.
  4. In Cloud Provider, select the Cloud Provider you set up in Harness Account Setup.
  5. Click Next.
  6. In Provision Type, select Already Provisioned. If you want to use a Harness Infrastructure Provisioner, select Dynamically Provisioned.
  7. Fill out the remaining infrastructure settings for your target deployment infrastructure. Here is an example that targets an AWS EC2 instance:
  8. Click SUBMIT. The Service Infrastructure is added. You will select this Service Infrastructure when you create the Deploy Workflow.

Next Step


How did we do?