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?
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.