allow .devfile.yaml

[maxandersen]

/kind feature

Which functionality do you think we should add?

similar to discussed in eclipse-che/che#14548 it is good when devfile.yaml does not need to be shown by default.

Why is this needed?

to make it easier to add support for odo and che without "polluting" users view.

[girishramnani]

allow .devfile.yaml would mean we have an option to change the default filename by which a devfile is downloaded i.e. devfile.yaml to .devfile.yaml and use that to create a component?

[maxandersen]

I don't know how that mechanics work - just that if devfile.yaml are not found and a.devfile.yaml are present then that should be used instead.

[sbose78]

@girishramnani , Yes.

[kadel]

If we start allowing .devfile.yaml then we need to make sure that there is only one devfile present in the directory. If both devfile.yaml and .devfile.yaml are present odo needs to error out.

The problem is described here eclipse-che/che#14548 (comment)

[gorkem]

FYI eclipse-che/che#17537

[kadel]

/triage ready
/priority medium

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/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.

[kadel]

/reopen
/lifecycle frozen
/remove-lifecycle rotten

This is still valid
devfile/api#61

[openshift-ci-robot]

@kadel: Reopened this issue.

In response to this:

/reopen
/lifecycle frozen
/remove-lifecycle rotten

This is still valid
devfile/api#61

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.

[dharmit]

Scope

• in the code just add an OR condition
• integration test up to just odo url create would suffice.

[dharmit]

/unassign

/assign @anandrkskd