Two devfile component deployed with same name, second component overrides the first one.

[adisky]

/kind discussion

What versions of software are you using?

Operating System:

Output of odo version:

How did you run odo exactly?

Actual behavior

If you try two create two devfile component with same, neither odo push nor odo create gives error.
e.g

• create a nodejs component
  $ odo create nodejs unique
  $ odo push
• create a springboot component with same name from a different dir
  $ odo create springboot unique
  $ odo push

odo push succeeds here, with springboot component overridden the nodejs component.

Expected behavior

odo create should give error, if the devfile component with same name already present on the cluster.

Any logs, error output, etc?

[girishramnani]

but this is a concious decision that you as a user are making, so isn't this acceptable?

[adisky]

i am not sure about the behavior here, but shouldn't odo create give error if you try to create component with same name?

[girishramnani]

Yeah I suppose so

[adisky]

got your point we are doing same in s2i, I do not see any downside of existing behavior too.
/close

[openshift-ci-robot]

@adisky: Closing this issue.

In response to this:

got your point we are doing same in s2i, I did not found any harm with this behavior.
/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.