-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix getting-started triggers #642
Conversation
@@ -1,4 +0,0 @@ | |||
apiVersion: v1 | |||
kind: Namespace |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deleted this -- the docs explicitly mention creating the namespace. The formerly commented out test was using this. I replaced it with a call to create the namespace in the test script.
The EventListener was referring to the Binding via `name` instead of `ref`. Also, run the getting-started examples as part of the e2e YAML tests. While this won't catch all issues with the examples, it should catch obvious syntax issues like this one. Fixes tektoncd#639 Fixes tektoncd#164 Signed-off-by: Dibyo Mukherjee <dibyo@google.com>
/lgtm /approval |
/lgtm |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wlynch 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:
Approvers can indicate their approval by writing |
Some of the Triggers content was moved in tektoncd/triggers#642, specifically: create-ingress.yaml and create-webhook.yaml These have been moved to the getting-started folder which broke the website sync script, blocking other changes. Update the sync config to point to the new paths to unblock other changes.
Some of the Triggers content was moved in tektoncd/triggers#642, specifically: create-ingress.yaml and create-webhook.yaml These have been moved to the getting-started folder which broke the website sync script, blocking other changes. Update the sync config to point to the new paths to unblock other changes.
Changes
The EventListener was referring to the Binding via
name
instead ofref
. Also, run the getting-started examples as part of the e2e YAML tests. While this won't catch all issues with the examples, it should catch obvious syntax issues like this one.Fixes #639
Fixes #164
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
/kind bug