support for optional pipeline time to live (TTL)

[marco-m]

What challenge are you facing?

Often you are setting up "test" or "proof-of-concept" pipelines. Their value expires in a few days.

Often it happens that you forget to destroy it: the pipeline stays around and, depending on what it contains, it can generate useless load and/or traffic.

If you have lots of pipelines, such forgotten pipelines will become almost invisible.

What would make this better?

If I could say something like

fly set-pipeline -p my-bright-idea --ttl=2d3h

I could merrily forget about my pipeline and Concourse would destroy it after 2d3h :-)

Behavior and testing considerations

• test what happens when a pipeline gets refreshed with another set-pipeline and TTL
• if a pipeline with TTL gets refreshed via set-pipeline, refresh should FAIL if refresh doesn't specify a TTL. Maybe a special value for TTL, like 0, means "remove TTL, this pipeline becomes normal, no more expiration"
• test that if a pipeline is destroyed OOB (eg user with fly, not TTL expiration), the TTL is cancelled at destruction time.

Are you interested in implementing this yourself?

Yes!

[vito]

I like it!