GalleyBytes/terraform-operator v0.9.0-pre3

v0.9.0-pre3 release

on GitHub

Changes in v0.9.0-pre3 since v0.9.0-pre2

Changes

• Default script image bumped to version 1.0.1 to take into account executing script from $TFO_MAIN_MODULE which was the behavior pre v0.9.0.

Breaking Changes

• taskOptions.affects changes to taskOptions.for in api. Affects felt awkward and didn't capture what I wanted; which was the tasks the taskOptions were "for".

For those who have used affects, it may be difficult to remove old resources. This little script can help remove old resources by deleteing them and then removing the finalizer:

NS=<namespace>
kubectl delete tf -n $NS --all --wait=false
kubectl get tf -oname -n $NS |
xargs -I% kubectl patch -n $NS % --type json -p '
	[
		{
			"op": "remove",
			"path":"/spec/taskOptions",
			"value": null
		},
		{
			"op": "remove",
			"path": "/metadata/finalizers",
			"value":  null
		}
	]'

Changes in v0.9.0-pre3 since v0.8.5

Features

• A new plugins field has been added which allows the configuration of custom pods to be started within a workflow.
• "Global environment variables" can be added to the controller pod which then gets read into every pod.

Changes

• The apiVersion has been updated from v1alpha1 to v1alpha2.
  • A new conversion webhook is automatically installed which converts old manifests to the new version
  • For the conversion, a new init container will generate and maintain a selfsigned cert requried when using a service reference webhook
  • A warning that v1alpah1 is not supported will be displayed if creating resources in the old apiVersion

Breaking Changes

• The exportRepo has been removed. The exportRepo feature will likely become an addon and maintainedin a different repo
• All new task container images (formerly known as runners) have been created. Task container images now have a separate repo. See terraform-operator-tasks.

Fixes

• If terraform apply fails, when the "apply" pod is deleted, the controller starts from the plan stage. Before it would try to just run apply again, but the terraform plan would be "stale" which prevented a generation from finishing.