improve concourse pipeline renaming process

[robwhitby]

Renaming a halfpipe pipeline can be confusing in Concourse, especially with versioned pipelines.

• when a pipeline is renamed it gets a new version file starting at 0.1.0.
• but the renamed pipeline still has history - it thinks it has already run the jobs for version 0.1.0 so they are not automatically triggered.

The current workaround is to manually update the version number (e.g. bump major version) to stop new runs clashing with history.

Can we do anything to improve this?

[robwhitby]

i have the start of an idea for the renaming pipelines problem

• add an optional field to halfpipe manifest id: <string>
• use that id as the version filename
• if someone runs halfpipe upload without the id we can generate a GUID and update the halfpipe file
• id defaults to name for existing pipelines so nothing breaks. If they want to rename they they set id: <old-name>

needs more thought but kind of works i think :thinking_face:

[robwhitby]

we should spike this to learn more

[robwhitby]

https:/springernature/halfpipe/tree/pipeline_id