Release v1.7.0

CLI

• Fixed zsh completions
• unipipe terraform updates status.yml to succeeded for service instances without any binding
• A UniPipe Terraform Runner docker container is now available. You can find the versioned containers
  here.
  It can be configured via a few environment variables and executes unipipe terraform every minute
  for the configured git repository. It also pulls changes from and pushes updated status.yml files,
  etc to the configured git repository. Using this UniPipe Terraform Runner together with the
  UniPipe Service Broker results in a fully functional service broker.
• Fixed mixed up plan and service column in unipipe list command. Service names are now shown
  in the Service column and plans are shown in the Plan column.
• Added manual parameter input to unipipe terraform processing. This can be used if before executing
  Terraform for a Service Instance, an operator needs to take some manual action and provide additional
  input to the Terraform module. This can be used to e.g. provide an IP range for a service instance of a
  networking service, if no IPAM solution is in place. The operator just needs to put a params.yml in
  the according instance folder. Once this file is available the unipipe terraform command will apply Terraform.
  Whether a service requires this manual input can be defined in the metadata of a Service Plan in the service catalog.
• Support usage of Terraform Backend for unipipe terraform command. If a backend.tf file exists in the service's
  terraform folder it is copied to the binding directory where Terraform is executed. No configuration of
  the backend.tf can be done. The file will be used as is. In order to separate the different tfstates in the backend,
  the unipipe terraform command uses Terraform Workspaces. A workspace will be created for every service binding.
  Credentials for accessing the backend have to be set via environment variables. If e.g. an azure backend is used,
  ARM_CLIENT_ID and ARM_CLIENT_SECRET have to be set.
• unipipe terraform now supports the full lifecycle of a service instance. If a service instance or its binding is
  deleted, the unipipe terraform command applies a terraform destroy to remove the instance again.
• It is now possible to add a --plan option to unipipe terraform, which executes the command basically as a dry-run.
  Instead of doing terraform apply, a terraform plan is executed and the console output shows the result of terraform plan.
  No status.yml is updated in this case.
• unipipe terraform provides the plan_id and plan_name as variables to the Terraform module.

OSB

• no changes