Custom link names and bindAsFiles option for SB#4729
Conversation
55a23f7 to
b3f1d32
Compare
b3f1d32 to
95ca61f
Compare
|
/retest |
95ca61f to
520ed67
Compare
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
/test psi-kubernetes-integration-e2e |
520ed67 to
d2863d2
Compare
|
/test psi-kubernetes-integration-e2e |
9c06c76 to
4981d4d
Compare
|
|
||
| func TestSearchLinkName(t *testing.T) { | ||
| tests := []struct { | ||
| ei *EnvInfo |
There was a problem hiding this comment.
Please add a test case name describing the test scenario.
| }) | ||
| }) | ||
|
|
||
| Context("When running an etcd operator backed service", func() { |
There was a problem hiding this comment.
I think these tests should be in https://github.com/openshift/odo/blob/main/tests/integration/operatorhub/cmd_service_test.go file. A similar linking scenario is already present in that file.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: feloy 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 |
Please add the steps to test the PR. |
|
/retest |
What type of PR is this?
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes #4693
PR acceptance criteria:
Unit test
Integration test
Documentation
Update changelog
I have read the test guidelines
TODO
How to test changes / Special notes to the reviewer:
On a cluster with some Operator backed services installed (for example etcdoperator.v0.9.4-clusterwide):