Update buildpacks-v3 template for latest lifecycle

[ameyer-pivotal]

Signed-off-by: Andrew Meyer ameyer@pivotal.io

Changes

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes docs (if user facing)
• Commit messages follow commit message best practices

See the contribution guide
for more details.

[ameyer-pivotal]

/assign @vdemeester

[vdemeester]

/ok-to-test

[vdemeester]

@ameyer-pivotal Thanks for the PR, but as is, it doesn't work, or more accurately the example can't work. A fix should allow this to work (with a different syntax) in the near future, but for now we should update the README with a working example.

[vdemeester]

I wonder how to handle the versionning, as this would only work a master/nightly pipeline deploy. I feel we should add some annotation (in the yaml) and some sort of ribbon (or warning), that this task currently only work on tektoncd/pipeline master, and will work with 0.6.0 and above.

[ameyer-pivotal]

I wonder how to handle the versionning, as this would only work a master/nightly pipeline deploy. I feel we should add some annotation (in the yaml) and some sort of ribbon (or warning), that this task currently only work on tektoncd/pipeline master, and will work with 0.6.0 and above.

@vdemeester By annotation, do you simply mean a comment, or something more formal? For the warning, what mechanism were you thinking specifically to display it?

[dlorenc]

@vdemeester By annotation, do you simply mean a comment, or something more formal? For the warning, what mechanism were you thinking specifically to display it?

A comment in the documentation would be great for now. I'll open an issue to create a more formal method.

[dlorenc]

#53 to track the version issue.

[vdemeester]

@vdemeester By annotation, do you simply mean a comment, or something more formal? For the warning, what mechanism were you thinking specifically to display it?

(Sorry I was off a few days) as @dlorenc said, right now a comment is fine. This is something we need to figure out for the long term 👼

[ameyer-pivotal]

@vdemeester @dlorenc Thanks for your response. I went ahead and added a compatibility note to the documentation. Please have a look and let me know if that works :)

[vdemeester]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ameyer-pivotal, 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 [vdemeester]

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