Task for creating GitHub deployments

[jace-ys]

Changes

This introduces a Task for creating GitHub deployments for a given
repository. This allows people who rely on GitHub deployment events
for their CD systems to be able create them from within a Tekton
pipeline.

This task is pretty much just a wrapper around the GitHub API for
creating deployments. The main params required are the ref
and environment for the deployment, and we fall back to the API's
defaults for the other params.

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
• Yaml file complies with yamllint rules.

See the contribution guide
for more details.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[tekton-robot]

Hi @jace-ys. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jace-ys]

Have a couple of things I'm uncertain about and would appreciate some feedback!

[jace-ys]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[vdemeester]

/ok-to-test

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ Jace Tan (08dcb23)

[jace-ys]

/retest

[vdemeester]

@jace-ys switched the base branch to master as it got merged with v1beta1 now 👼

[sm43]

Also if you could add the task with all the files in the task directory

  ./task/         👈 the kind of the resource 
      /argocd       👈 definition file must have same name
        /0.1
          /README.md     👈 [optional] since there can be a fallback
          /argocd.yaml   👈 the file name must be resource name
        /0.2/...
      /golang-build
        /0.1
          /README.md
          /golang-build.yaml

Please see : #389
Let me know if you need help.

[jace-ys]

Thanks @sm43 for the heads-up. I have done this now and rebased again latest master 🙂

[vinamra28]

just a small fix otherwise looks good to me

[vinamra28]

/cc @chmouel
This PR looks good to me could you please have a look at it for once 😅 and merge this

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[jace-ys]

Sorry for the delay with fixing up this PR! Totally forgot this was still lingering about.

/remove-lifecycle stale

[vinamra28]

Suggested change

	image: registry.access.redhat.com/ubi8/ubi:latest
	image: registry.access.redhat.com/ubi8/ubi:8.2

[jace-ys]

I see that the other github tasks still use latest but I guess that they should all be pinned as well?

[vinamra28]

There is a PR #519 which will pin the version of all the tasks :)

[jace-ys]

Hi @vinamra28 and @divyansh42,

Thanks for your feedback! I have taken them into account and adjusted the PR accordingly.

Let me know what you think 😄

[divyansh42]

Looks good to me!
/cc @chmouel

[vinamra28]

/cc @chmouel

[chmouel]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chmouel, vinamra28

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 [chmouel,vinamra28]

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

[vinamra28]

/lgtm

[jace-ys]

thanks all 🙌