-
Notifications
You must be signed in to change notification settings - Fork 111
fix(convert): When converting devfile v1 to v2, registryUrl attribute is forgotten #1115
Conversation
… is forgotten Related to eclipse-che/che#19829 Change-Id: Ia7dd9aec31f0c6b5326c4d645bfbf4f87ac8e69e Signed-off-by: Florent Benoit <fbenoit@redhat.com>
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che on K8S (minikube v1.1.1)
Eclipse Che QE channel: https://mattermost.eclipse.org/eclipse/channels/eclipse-che-qe |
Codecov Report
@@ Coverage Diff @@
## master #1115 +/- ##
==========================================
+ Coverage 29.45% 32.26% +2.81%
==========================================
Files 277 281 +4
Lines 9336 9551 +215
Branches 1380 1435 +55
==========================================
+ Hits 2750 3082 +332
+ Misses 6487 6373 -114
+ Partials 99 96 -3
Continue to review full report at Codecov.
|
would be great to back port it for 7.30.x so that it would land in the 2.9 version of product |
[crw-ci-test] |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che on K8S (minikube v1.1.1)
Eclipse Che QE channel: https://mattermost.eclipse.org/eclipse/channels/eclipse-che-qe |
Happy path worked on ubi8 next |
[crw-ci-test --rebuild] |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che on K8S (minikube v1.1.1)
Eclipse Che QE channel: https://mattermost.eclipse.org/eclipse/channels/eclipse-che-qe |
[crw-ci-test --rebuild] |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che on K8S (minikube v1.1.1)
Eclipse Che QE channel: https://mattermost.eclipse.org/eclipse/channels/eclipse-che-qe |
What does this PR do?
Devfile v1 is converted internally to devfile V2 to expose new API to plug-ins/extensions but
registryUrl
field was not handled.Thus, if the editor needs to write the file at some point, this information is removed
Screenshot/screencast of this PR
What issues does this PR fix or reference?
Fixes eclipse-che/che#19829
How to test this PR?
Look at the unit test (now the field is preserved)
Another manual way : Add a custom component using
registryUrl
field, then starts the workspace, install another plug-in and now look at the updated devfile. New plug-in should be there but also theregistryUrl
should be still therePR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or reference
andHow to test this PR
completedReviewers
Reviewers, please comment how you tested the PR when approving it.
Happy Path Channel
HAPPY_PATH_CHANNEL=next
Change-Id: Ia7dd9aec31f0c6b5326c4d645bfbf4f87ac8e69e
Signed-off-by: Florent Benoit fbenoit@redhat.com