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

Create proposal for defining a dockerfile component on alizer #1160

Closed
Tracked by #1159
thepetk opened this issue Jun 30, 2023 · 2 comments · Fixed by devfile/alizer#3
Closed
Tracked by #1159

Create proposal for defining a dockerfile component on alizer #1160

thepetk opened this issue Jun 30, 2023 · 2 comments · Fixed by devfile/alizer#3
Assignees
Labels
area/alizer Enhancement or issue related to the alizer repo

Comments

@thepetk
Copy link
Contributor

thepetk commented Jun 30, 2023

Which area/kind this issue is related to?

/area alizer

Issue Description

Related: EPIC #1159

To improve port detection around dockerfiles, we need to consider cases where a dockerfile may not be inside a detected component. This requires a new component definition which this proposal will focus on.

Target date: July 04

@openshift-ci openshift-ci bot added the area/alizer Enhancement or issue related to the alizer repo label Jun 30, 2023
@thepetk thepetk moved this to In Progress 🚧 in Devfile Project Jun 30, 2023
@thepetk thepetk moved this from In Progress 🚧 to In Review 👀 in Devfile Project Jun 30, 2023
@thepetk
Copy link
Contributor Author

thepetk commented Jun 30, 2023

Follow old comments on redhat-developer/alizer#244

@mike-hoang
Copy link
Contributor

PR moved from redhat-developer/alizer to devfile/alizer#3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/alizer Enhancement or issue related to the alizer repo
Projects
Status: Done ✅
Development

Successfully merging a pull request may close this issue.

2 participants