Skip to content

sequence and parallel conversion webhook#2611

Merged
knative-prow-robot merged 10 commits into
knative:masterfrom
lionelvillard:flows-v1alpha1-v1beta1
Feb 21, 2020
Merged

sequence and parallel conversion webhook#2611
knative-prow-robot merged 10 commits into
knative:masterfrom
lionelvillard:flows-v1alpha1-v1beta1

Conversation

@lionelvillard
Copy link
Copy Markdown
Contributor

Proposed Changes

  • Add support for v1alpha1<->v1beta1 for sequences and parallels

Release Note

- 🎁 Add new feature
* Add support for Sequence and Parallel v1alpha1<->v1beta1

@knative-prow-robot knative-prow-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 20, 2020
@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Feb 20, 2020
@knative-prow-robot knative-prow-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 20, 2020
@knative-prow-robot knative-prow-robot removed the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Feb 20, 2020
@googlebot
Copy link
Copy Markdown

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@knative-prow-robot knative-prow-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Feb 20, 2020
@googlebot googlebot added cla: no Indicates the PR's author has not signed the CLA. and removed cla: yes Indicates the PR's author has signed the CLA. labels Feb 20, 2020
@knative-prow-robot knative-prow-robot added the area/test-and-release Test infrastructure, tests or release label Feb 20, 2020
@googlebot
Copy link
Copy Markdown

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@googlebot googlebot removed the cla: no Indicates the PR's author has not signed the CLA. label Feb 20, 2020
@knative-prow-robot knative-prow-robot removed the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Feb 20, 2020
@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Feb 20, 2020
@knative-prow-robot knative-prow-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Feb 20, 2020
@lionelvillard lionelvillard changed the title [WIP] sequence and parallel conversion webhook sequence and parallel conversion webhook Feb 20, 2020
@knative-prow-robot knative-prow-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 20, 2020
@lionelvillard
Copy link
Copy Markdown
Contributor Author

/assign @vaikas

@knative-prow-robot knative-prow-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Feb 20, 2020
Copy link
Copy Markdown
Contributor

@vaikas vaikas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!! Just a thought about removing the schema section which has been giving us some trouble :( Also if you wouldn't mind v1beta1->v1alpha1->v1beta1 tests that would be awesome :)

Comment thread config/core/resources/parallel.yaml Outdated
type: string
minLength: 1
name:
type: string
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You'll probabaly beed the namespace here as well, or it won't necessarily roundtrip properly. We've had quite a few of these failures because things have drifted over time. Since you need to rebase anyways, maybe just get rid of the schemas. Look for example at inmemorychannel.yaml to see what it looks like without these. You need to add an overall validation section. Plan is to then autogenerate these and merge them rather than code them by hand.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok done.

Still having an issue with the AdmissionController that cannot decode the new object. This happens just before defaulting. Not sure why yet

},
},
}, {
name: "full configuration",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We started to also do tests where we start with v1beta1 -> v1alpha1 ->v1beta1, would you mind adding those tests as well? you can see for example pkg/apis/messaging/v1alpha1/channel_conversion_test.go.

// for the namespace (or cluster, in case there are no defaults for the namespace).
// +optional
ChannelTemplate *eventingduckv1alpha1.ChannelTemplateSpec `json:"channelTemplate,omitempty"`
ChannelTemplate *messagingv1beta1.ChannelTemplateSpec `json:"channelTemplate,omitempty"`
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@lionelvillard
Copy link
Copy Markdown
Contributor Author

/hold

adding v1beta1->v1alpha1->v1beta1 tests

@knative-prow-robot knative-prow-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 21, 2020
@knative-metrics-robot
Copy link
Copy Markdown

The following is the coverage report on the affected files.
Say /test pull-knative-eventing-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/apis/flows/v1alpha1/parallel_conversion.go Do not exist 100.0%
pkg/apis/flows/v1alpha1/sequence_conversion.go Do not exist 100.0%
pkg/apis/flows/v1beta1/parallel_conversion.go Do not exist 100.0%
pkg/apis/flows/v1beta1/sequence_conversion.go Do not exist 100.0%

@vaikas
Copy link
Copy Markdown
Contributor

vaikas commented Feb 21, 2020

/lgtm
/approve

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 21, 2020
@knative-prow-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lionelvillard, vaikas

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [lionelvillard,vaikas]

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

@lionelvillard
Copy link
Copy Markdown
Contributor Author

/hold cancel

@knative-prow-robot knative-prow-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 21, 2020
@knative-prow-robot knative-prow-robot merged commit dd11517 into knative:master Feb 21, 2020
@nachocano nachocano mentioned this pull request Jul 8, 2020
8 tasks
@lionelvillard lionelvillard deleted the flows-v1alpha1-v1beta1 branch August 28, 2020 15:38
@lionelvillard lionelvillard restored the flows-v1alpha1-v1beta1 branch September 3, 2020 15:42
@lionelvillard lionelvillard deleted the flows-v1alpha1-v1beta1 branch September 3, 2020 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/test-and-release Test infrastructure, tests or release cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants