conditional TASK_DEFINITION variable in pipe

[rushabh]

I want to create new task definition only when some environment variable in the files is updated. Pipe has variable TASK_DEFINITION which i am conditionally setting via script. If TASK_DEFINITION is empty i don't want to create new revision. Just do a force deployment. how can i achieve this?

[Aron Gombas _Midori_]

Although you can add conditions to pipeline steps, those aren't very powerful as you can only test for which files were included in the change.

What you could do is, that basically your steps are UNIX commands, and in the shell you can test for existence of a environment variable in a dead-simple way.