-
Notifications
You must be signed in to change notification settings - Fork 71
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
Migrate to apiVersion v1 from v1aplha1 #1566
Migrate to apiVersion v1 from v1aplha1 #1566
Conversation
80305d4
to
eef02f0
Compare
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.
Looks good, but validator needs to be fixed.
right. We need the camel k crds to be fixed first so that it exports types correctly. I just reported apache/camel-k#4683 |
also I think #1579 shoudl be fixed first and then rebase this PR to ensure there are no regressions |
Set as draft while we wait for the fix in yaks and the camel-kamelet api |
#1579 is fixed. |
while fixing #1579 I realized that Camel JBang 4.0 is not able to handle |
Right now YAKS tests use As mentioned earlier Camel JBang 4.0 runtime may not be able to handle Pipe resources though |
There was a part of Camel Core/JBang which was able to use Pipe (if i remember well) |
If supporting Pipe is not completely working, we should wait to merge this one and release with just camel 4.0.0 release upgrade. Once everything is in place we could merge this one and release a 4.0.1 |
The migration of KameletBinding to Pipe sounds like an API break. Having it in a major version sounds better. Is it a possibility of not releasing the Kamelets 4.0.0 and jump directly to 4.0.1 which will pick Camel Core/JBang 4.0.1 and Camel K 2.0.1? |
I don't think it's good to not have a 4.0.0 release. But if the pipe upgrade is incomplete this PR cannot be merged |
80cfead
to
f4a2aa7
Compare
@davsclaus what are your thoughts on this? |
This would require Camel 4.0.1 to work with camel-jbang for the kamelet binding -> pipe renaming. The v1alpha1 -> v1 works on 3.x and 4.x and is no problem. |
So are you suggesting to release as is and merge this one only with 4.0.1? |
No its okay but just a known issue for camel-jbang with 4.0.0 that you need to use KameletBinding as the name. We will do 4.0.1 next month so it not very long time |
And Pipe will work on camel-k 2.0 |
Ok, I'll add this one before releasing, together with some new Kamelets |
f4a2aa7
to
93ce4f6
Compare
Rebased and migrated also newly added kamelet to be ready to integrate Camel K 2.0.1 release asap when it will be released (currently in vote) |
Thanks |
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.
Had a look into the YAKS tests and added some comments why I think those are failing
.github/workflows/yaks-tests.yaml
Outdated
@@ -42,7 +42,7 @@ concurrency: | |||
|
|||
env: | |||
YAKS_VERSION: 0.16.0 | |||
YAKS_RUN_OPTIONS: "--timeout=15m --local -e YAKS_CAMELK_MAX_ATTEMPTS=10 -e YAKS_JBANG_CAMEL_VERSION=4.0.0 -e YAKS_JBANG_KAMELETS_VERSION=4.0.0-SNAPSHOT -e YAKS_JBANG_KAMELETS_LOCAL_DIR=../../../kamelets -e YAKS_KAMELET_API_VERSION=v1alpha1" |
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.
Question regarding -e YAKS_KAMELET_API_VERSION=v1alpha1
Is Camel 4.0.0 able to handle Pipe resources? Last time I checked this raised me some errors because Pipe has not been recognized by Camel JBang
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 think it is supported completely from 4.0.1
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.
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.
yes, 4.0.1 should handle it
I updated YAKS_JBANG_CAMEL_VERSION=4.0.0
to YAKS_JBANG_CAMEL_VERSION=4.0.1
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.
Camel 4.0.1 has not been released yet.
Will try with 4.0.1-SNAPSHOT but do not know how it will be able to pick it up.
it seems that Camel Jbang 4.0.0 is still used:
which should explain that it is still failing:
EDIT: Camel 4.0.1 has not been released yet |
I don't know if it's really feasible to have yaks tests passing. |
We need to take a decision, wait for 4.0.1 and introduce this stuff only at that point or merge without yaks tests, which it's not good anyway. |
It's not YAKS fault. |
Can't we use Camel JBang 4.0.1-SNAPSHOT? |
I don't think so, it doesn't pick it up.
|
🤔 we would need to tell JBang to use this repository, too when resolving Maven artifacts. I think this must be added to the YAKS Camel JBang call. I can do this in YAKS. Besides that I think we could also just keep using KameletBinding on the YAKS tests. Camel JBang is supposed to support both Pipe and KameletBinding and in the end we are keen to test the Kamelets here not the runtime |
Yes, this is another possibility and then switch after 4.0.1 @apupier could you do that? |
if i remember well, it is this repository which helped to catch that Camel JBang was not ready for Pipes so even if it was not be the initial purpose, it sounds like the current best way to test it. |
f705a47
to
c756273
Compare
recreated branch on top of main (was too many conflicts to fixed, easier to redo). |
fixes apache#1562 * Renamed kind in CRDs * Renamed KameletBinding examples by changing suffix -binding to -pipe * Renamed folder and file names having binding * Updated doc * Updated Yaks tests Signed-off-by: Aurélien Pupier <apupier@redhat.com>
c756273
to
f15f942
Compare
rebased on main branch now that Camel 4.0.1 has been released but I think it will stil require apache/camel#11550 |
@christophd can you have a look? |
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.
Have had a look into the failing YAKS test. I think it should be fixed with adding "camel:cloudevents" dependency
camel:cloudevents dependency is required because the pipe uses the CloudEvents data type transformers from Camel
YES, tests are fixed! |
Yuppie! |
Let's merge, great work @apupier @christophd |
fixes #1562
apiVersion
fromcamel.apache.org/v1alpha1
tocamel.apache.org/v1
KameletBinding
to PipeKameletBinding
examples by changing suffix-binding
to-pipe