Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for devfile, port and name detection #2781

Closed
kadel opened this issue Mar 8, 2023 · 1 comment · Fixed by #3292
Closed

Add support for devfile, port and name detection #2781

kadel opened this issue Mar 8, 2023 · 1 comment · Fixed by #3292
Assignees
Milestone

Comments

@kadel
Copy link
Member

kadel commented Mar 8, 2023

Odo uses Alizer to suggest the best devfile for the users, together with the name and ports used by the application.

The extension should use this information to list Devfile detected by Alizer in Devfile stack selection first and suggest the default name as detected by Alizer (name field is currently missing in the odo analyze bit it will be added redhat-developer/odo#6649)

Also, part of the "Create component" flow should be selecting the correct port; the default ports should be preselected based on the odo analyze output.

As and example of how it can be done, check odo init flow

$ odo analyze -o json
[
	{
		"devfile": "go",
		"devfileRegistry": "DefaultDevfileRegistry",
		"ports": [
			9000
		],
		"devfileVersion": "1.0.2"
	}
]
@mohitsuman mohitsuman added this to the 1.4.0 milestone Mar 23, 2023
@mohitsuman mohitsuman modified the milestones: 1.4.0, 1.5.0 May 17, 2023
@mohitsuman mohitsuman modified the milestones: 1.5.0, 1.6.0 Jun 2, 2023
@msivasubramaniaan
Copy link
Collaborator

msivasubramaniaan commented Jun 21, 2023

Moved this ticket to backlog and out of sprint, as odo has to provide an option to create component with user provided port redhat-developer/odo#4448

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment