odo link and odo unlink write to devfile without deploying to cluster#4819
Conversation
2449b9e to
877186b
Compare
|
/test v4.7-integration-e2e |
f8ed8dd to
c68988a
Compare
|
/test psi-kubernetes-integration-e2e |
c6a6f2e to
34e04ef
Compare
dharmit
left a comment
There was a problem hiding this comment.
/approve
@feloy thanks for this PR! An amazing result of this PR is that it takes a devfile with component, service and link information and doing odo push creates it all on the cluster. It's an experience that we had been talking about achieving since a LONG time!
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dharmit The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| }) | ||
| } | ||
|
|
||
| list := helper.CmdShouldPass("odo", "catalog", "list", "services") |
There was a problem hiding this comment.
Can we use the new runner functions in tests.
Functions mentioned in this PR will remove be removed.
I would request you to use those instead of the old ones.
|
/test psi-kubernetes-integration-e2e |
| When("a link is created between the component and the service", func() { | ||
|
|
||
| BeforeEach(func() { | ||
| helper.CmdShouldPass("odo", "link", svcFullName) | ||
| }) | ||
|
|
||
| When("odo push is executed", func() { | ||
| BeforeEach(func() { | ||
| helper.CmdShouldPass("odo", "push") | ||
| oc.PodsShouldBeRunning(commonVar.Project, componentName+`-app-.[a-z0-9-]*`) | ||
| }) |
There was a problem hiding this comment.
@feloy why are we separating odo link and odo push in two when do we want to add a test in between these two scenario?
Can we use this instead? (asking this because I see only one test case getting tested under two layer of when)
When("a link is created between the component and the service and odo push is executed", func() {
BeforeEach(func() {
helper.CmdShouldPass("odo", "link", svcFullName)
helper.CmdShouldPass("odo", "push")
oc.PodsShouldBeRunning(commonVar.Project, componentName+`-app-.[a-z0-9-]*`)
})
There was a problem hiding this comment.
Yes, no problem, we can use your version, as there is no test between the two steps.
6461a96 to
ec91a51
Compare
5677500 to
4be820c
Compare
|
/test psi-kubernetes-integration-e2e |
4be820c to
12fed53
Compare
5cac471 to
f8592f0
Compare
|
@feloy I noticed a funny thing with Steps to reproduce -
I have tried this a few times and was always able to reproduce, can you check it once? |
|
Ah okay. Apart from it being dependent on this PR, is it ready for testing or still a WIP? |
|
/test psi-kubernetes-integration-e2e |
1 similar comment
|
/test psi-kubernetes-integration-e2e |
|
[kubectl] The connection to the server -IP REDACTED-:8443 was refused - did you specify the right host or port? /test psi-kubernetes-integration-e2e |
|
Flaky test /test v4.7-integration-e2e |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
What type of PR is this?
/kind feature
What does this PR do / why we need it:
odo linkstores link info in devfileodo linkdoes not create sbrodo linkfails if link with same name already existsodo unlinkremoves link info from devfileodo pushcreates sbr and makes the container run correctlyodo pushdeletes sbr and makes the container run correctlypossibility to create link to a non deployed serviceWhich issue(s) this PR fixes:
Fixes #4208
Fixes #4750
Fixes #4768
PR acceptance criteria:
Unit test
Integration test
Documentation
Update changelog
I have read the test guidelines
How to test changes / Special notes to the reviewer: