-
Notifications
You must be signed in to change notification settings - Fork 600
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
Update Sequence to use correct conditions. #5369
Conversation
Codecov Report
@@ Coverage Diff @@
## main #5369 +/- ##
==========================================
- Coverage 82.65% 82.61% -0.05%
==========================================
Files 194 194
Lines 6002 6004 +2
==========================================
- Hits 4961 4960 -1
- Misses 717 720 +3
Partials 324 324
Continue to review full report at Codecov.
|
The following is the coverage report on the affected files.
|
@@ -124,10 +124,11 @@ type SequenceStatus struct { | |||
// Matches the Spec.Steps array in the order. | |||
ChannelStatuses []SequenceChannelStatus `json:"channelStatuses"` | |||
|
|||
// AddressStatus is the starting point to this Sequence. Sending to this | |||
// Address is the starting point to this Sequence. Sending to this |
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.
Just to make sure I understand correctly. This is equivalent because we inlined AddressStatus before and instead of inlining you changed it to be explicit? Is there a reason why this is not a pointer like what AddressStatus has?
https://github.com/knative/pkg/blob/main/apis/duck/v1/addressable_types.go#L64
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.
I am doing what Broker does, we have both styles and because the inner url is a pointer, it seems like the wrapper to the addressable could be allowed to be not a pointer?
We should pick a style and make it consistent. The root issue might be https://github.com/knative/pkg/blob/main/apis/duck/v1/addressable_types.go#L64 has URL as not optional
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.
Yeah, should've been clearer. I saw there being inconsistencies also. But just wanted to make sure that my understanding is that there are no changes to wire format. We should probably vet these to make sure they are consistent, and make sure that we comment the duck properly since it says there to embed it like this (well, that's how I read it still).
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vaikas 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 |
Fixes #4929
False
toUnknown
when setting non-terminal conditions./kind cleanup