From d1e74a85090706bec60ae27492e6a43b759fdfbc Mon Sep 17 00:00:00 2001 From: Dominik Henneke Date: Wed, 19 May 2021 17:30:16 +0200 Subject: [PATCH] Remove unintended paragraph in the scaffolder template migration document Signed-off-by: Dominik Henneke --- .../migrating-from-v1alpha1-to-v1beta2.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/features/software-templates/migrating-from-v1alpha1-to-v1beta2.md b/docs/features/software-templates/migrating-from-v1alpha1-to-v1beta2.md index c59eb79be7..25ff2a2f3a 100644 --- a/docs/features/software-templates/migrating-from-v1alpha1-to-v1beta2.md +++ b/docs/features/software-templates/migrating-from-v1alpha1-to-v1beta2.md @@ -14,12 +14,11 @@ steps which was pretty hard to extend and add new functionality to, difficult to re-use logic between templates. There used to be a fixed pipeline of `preparers`, `templaters`, and `publishers`, which were defined by the backend and needed to be run for each template. This is now changed, to give the -template total control over what - -should be executed as part of the templating run. This makes templates a little -more declarative as you can now register different `actions` or `functions` with -the `scaffolder-backend` which you then can decide how, and in what order, to -run using the template definition YAML file. +template total control over what should be executed as part of the templating +run. This makes templates a little more declarative as you can now register +different `actions` or `functions` with the `scaffolder-backend` which you then +can decide how, and in what order, to run using the template definition YAML +file. We've also made some improvements, and added some helpers to work with cookiecutter. The skeleton for a template can now be stored in a different place