Add command to Task.BuildSep.Steps in all example…

[vdemeester]

… also the guestbook integrationTestInDocker taskref name.

Fixes #202

Signed-off-by: Vincent Demeester [email protected]

[tejal29]

You have my LGTM
I am going to defer this to @bobcatfish.
I remember her saying this might not be required because we have some plan to extract the entry point for an image if command is not present.
In spite of that, this is good change which demonstrates good practice. (Users of task don't need to guess the command or look in to the image to figure out what the entry point is)

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tejal29, vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tejal29]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[bobcatfish]

Thanks for doing this @vdemeester !

I remember her saying this might not be required because we have some plan to extract the entry point for an image if command is not present.
In spite of that, this is good change which demonstrates good practice. (Users of task don't need to guess the command or look in to the image to figure out what the entry point is)

In #183 @tanner-bruce is making it so that if there is no command, the controller will check the image to see if there is an entrypoint and use that.

That being said there are still caveats to that approach (e.g. if the image is in a private docker registry, or if the image changes b/w when the controller looks at it and the node pulls it) so i think we should strongly encourage explicitly providing command

/lgtm

[bobcatfish]

nice :D