v0.23.1

Pipeline Enhancements

Notes:

• The Norm team (pcf-pipelines team) created a new docker image called pcfnorm/rootfs which we have started using with v23.1 (replacing czero/rootfs with pcfnorm/rootfs). We will also started versioning this image.
• The OpenStack Install Pipeline was not tested in this release; use the pipeline with caution

Install PCF Pipelines

• (ALL) Self-signed certs generated by the pipelines are now being signed with SHA-256 signatures story
• (ALL) Enhanced the pipelines to make system_domain and apps_domain configurable story
• (ALL) Removed erroneous params opsman_client_id and opsman_client_secret from the install pipelines story
• (ALL) Changed the Point of Entry ssl params to poe_ssl_name1, poe_ssl_cert1, and poe_ssl_key1, allowing up to three param entries story
• (ALL) Changed the Credhub Encryption Key params to credhub_encryption_key_name_1, credhub_encryption_key_1, allowing up to three param entries story
• (AWS) Fix such that the Terraform scripts for the load balancer have more sensible defaults for health_check: interval and health_check: healthy_thresholdstory
• (AWS) Fix to Terraform scripts - now the load balancer health_check targets the correct protocol, endpoint, and port story
• (Azure) Make configurable Ops Manager's private IP configurable; introduced a new param called azure_opsman_priv_ip story
• (Azure) Locked the Azure Provider version in our Terraform scripts to use 1.0.0 story
• (vSphere) Fixed a minor bug whereby the params.yml contained inverted commas which could cause issues when deploying the pipeline story
• (vSphere) Fix to accept the spaces in a resource pool name or the Ops Manager vm name story
• (vSphere, GCP) Fix such that the Ops Manager --> Create Networks --> Service Network checkbox is only checked for Dynamic Services network story

Upgrade Pipelines

• (upgrade-tile) Added a new param enable_errand which allows you to disable, enable, or leave the state of errands as-is when doing a upgrade to a patch release story

• (upgrade-ops-man; GCP and Azure) Fixes a Ops Manager disk size limitation by adding a new param pcf_opsman_disk_size_in_gb, allowing you to set the disk size for the new Ops Man vm* story

  *Note: For AWS and vSphere, the original disk size is preserved; you cannot set the disk size using the new parameter. For AWS, we've added this param in error it will be removed in the next release.

Param changes introduced in pcf-pipelines v0.23.1

Pipeline	Param	Notes
install-pcf	opsman_client_id	ALL; removed erroneous param
install-pcf	opsman_client_secret	ALL; removed erroneous param
install-pcf	poe_ssl_name1	ALL; up to three entries; renamed from networking_poe_ssl_certs
install-pcf	poe_ssl_cert1	ALL; up to three entries; renamed from networking_poe_ssl_certs
install-pcf	poe_ssl_key1	ALL; up to three entries; renamed from networking_poe_ssl_certs
install-pcf	credhub_encryption_key_name_1	ALL; up to three entries; renamed from credhub_encryption_keys
install-pcf	credhub_encryption_key_1	ALL; up to three entries; renamed from credhub_encryption_keys
install-pcf	azure_opsman_priv_ip	Azure; new param
install-pcf	system_domain	AWS, GCP; new param
install-pcf	apps_domain	AWS, GCP; new param
install-pcf	is_service_network	vSphere; removed param
upgrade-ops-manager	pcf_opsman_disk_size_in_gb	GCP and Azure; new param
upgrade-tile	enable_errands	new param