Bug 2032516 - Not able to import git repo with .devfile.yaml
Summary: Not able to import git repo with .devfile.yaml
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.10.0
Assignee: Rohit Rai
QA Contact: spathak@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-14 15:44 UTC by Rohit Rai
Modified: 2022-03-10 16:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:33:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 10670 0 None open Bug 2032516: Add support for checking .devfile.yaml during strategy detection 2021-12-15 16:39:43 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:34:19 UTC

Description Rohit Rai 2021-12-14 15:44:47 UTC
Description of problem: Currently, our import from git flow only looks for a devfile.yaml file. 


Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. Got to git import form.
2. Enter https://github.com/rohitkrai03/devfile-sample in the git repo URL field.


Actual results:
The import strategy detection only looks for devfile.yaml and thus fails and suggests Dockerfile strategy.

Expected results:
We should first look for devfile.yaml, and if that doesn't exist, look for a .devfile.yaml

Additional info:

Comment 3 Mohammed Saud 2021-12-30 18:58:20 UTC
Verified on:
Version: 4.10.0-0.nightly-2021-12-23-153012
Browser: Firefox 95

Comment 6 errata-xmlrpc 2022-03-10 16:33:57 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0056


Note You need to log in before you can comment on or make changes to this bug.