Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[cloudevents] Controller Integration Roadmap #830

Open
1 of 6 tasks
waveywaves opened this issue Feb 8, 2022 · 2 comments
Open
1 of 6 tasks

[cloudevents] Controller Integration Roadmap #830

waveywaves opened this issue Feb 8, 2022 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@waveywaves
Copy link
Member

waveywaves commented Feb 8, 2022 •
edited

Feature request

This issue tracks the requirements for the cloudevents controller to be in a position to be integrated with Tekton Pipeline as a standalone controller.

  • [cloudevents] Supported Tekton Pipeline Cloudevents format #835
  • Send TaskRun and Run events
  • Relay cloudevents from one controller to the others (to triggers, results etc.)
  • Stay up to date with CDEvents Format
  • Stabilize cloudevents controller before integration
  • TEP for replacing this controller with Tekton Pipeline cloudevents functionality
@waveywaves waveywaves added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 8, 2022
@waveywaves waveywaves mentioned this issue Feb 8, 2022
Open
@tekton-robot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
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 with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 8, 2022
@tekton-robot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 8, 2022
@afrittoli afrittoli added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jul 18, 2022
@afrittoli afrittoli mentioned this issue Jul 18, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
Tekton Community Roadmap
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
3 participants
@afrittoli @waveywaves @tekton-robot