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.

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

Figure out the appropriate fields in v1beta1 SubscribableStatus. #2416

Closed
vaikas opened this issue Jan 21, 2020 · 2 comments
Closed

Figure out the appropriate fields in v1beta1 SubscribableStatus. #2416

vaikas opened this issue Jan 21, 2020 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Milestone

Comments

@vaikas
Copy link
Contributor

vaikas commented Jan 21, 2020

Describe the bug
As part of the work in:
#2373
and in particular: Subscribable duck type in the Subscribable.Status.Subscribers[] array, there was a question about if there's enough fields there to convey enough information and if the fields are aptly named. In order to make progress on the major parts, we're going to restrict that struct conversation to this issue.

@n3wscott

@vaikas vaikas added the kind/bug Categorizes issue or PR as related to a bug. label Jan 21, 2020
@vaikas
Copy link
Contributor Author

vaikas commented Jan 22, 2020

This also applies in Sequence / Parallel, since they are exposed there in a similar fashion.

This was referenced Jan 22, 2020
@grantr grantr added this to the Backlog milestone Aug 24, 2020
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants