[TEP-0093] Add sign and verify to tektont cli
Changes
This commit adds sign and verify as subcommands for task and pipeline. Examples:
tkn task sign examples/example-task.yaml -K=cosign.key -f=signed.yaml
tkn task verify examples/signed.yaml -K=cosign.pub
Signed-off-by: Yongxuan Zhang [email protected]
/kind feature
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you review them:
- [ ] Includes tests (if functionality changed/added)
- [ ] Run the code checkers with
make check - [ ] Regenerate the manpages, docs and go formatting with
make generated - [ ] Commit messages follow commit message best practices
See the contribution guide for more details.
Release Notes
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign pradeepitm12 after the PR has been reviewed.
You can assign the PR to them by writing /assign @pradeepitm12 in a comment when ready.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
cc @concaf
I wonder if we should "put" those commands under experimental (see https://github.com/tektoncd/cli/pull/1575). Otherwise, nice ! /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: vdemeester
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [vdemeester]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
looks good :)
I wonder if we should "put" those commands under experimental (see #1575). Otherwise, nice ! /approve
Yes that sounds good! I will put them under experimental! But should we merge that PR first?
/retest
I wonder if we should "put" those commands under experimental (see #1575). Otherwise, nice ! /approve
Yes that sounds good! I will put them under experimental! But should we merge that PR first?
We should probably merge #1575 first indeed 👼🏼 cc @pradeepitm12 @piyush-garg
please fix typo -- "tekton", not "tektont" in the title
/lgtm