No pre check is done for existence of same component in the cluster

[amitkrout]

/kind bug

What versions of software are you using?

Operating System:
supported
Output of odo version:
master

How did you run odo exactly?

$ odo create nodejs backend --context
 /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/ 
--project test123
$ odo push --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/
$ odo component list --context
  /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/
APP     NAME        TYPE       SOURCE        STATE
app     backend     nodejs     file://./     Pushed           -------------- Looks good

$ odo create python backend --context 
/Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/ 
--project test123
$ odo push --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/python/

$ odo component list --context  /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/
APP     NAME        TYPE       SOURCE        STATE
app     backend     python     file://./     Pushed  <----- nodejs component is replaced 

$ odo component list --context  /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/python/
APP     NAME        TYPE       SOURCE        STATE
app     backend     python     file://./     Pushed  <----- nodejs component is replaced

Actual behavior

Replacing the deployed component of same name

Expected behavior

Should throw error of something like
There is already a component of same name exist in the same app and in same namespace.

Any logs, error output, etc?

[amitkrout]

/priority high

[kadel]

I'm afraid that with the current architecture this is impossible to solve.

If you push component with the same name and with the same application to the same project it will get replaced.

[kadel]

/triage unresolved
/close

[openshift-ci-robot]

@kadel: Closing this issue.

In response to this:

/triage unresolved
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.