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.

Sign up for GitHub

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

Jump to bottom

Provide ability to map component to containerName #14280

Closed
RomanNikitenko opened this issue Aug 19, 2019 · 1 comment
Closed

Provide ability to map component to containerName #14280

RomanNikitenko opened this issue Aug 19, 2019 · 1 comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Milestone
7.2.0

Comments

@RomanNikitenko
Copy link
Member

Is your task related to a problem? Please describe.

We have opportunity to define a component for che commands in devfile.
In runtime we get something like:

tasks_question

So we have info about component and target containerName in attributes for a command.

But I don't know way how we can map component and containerName using machines object in runtime. For example, if user changes the label for a task or defines in task.json component for a new task - how we can map it to corresponding containerName?

Describe the solution you'd like

It would be great to have some attributes for machines object in runtime to have ability to map
component and corresponding containerName.

Describe alternatives you've considered

Additional context

I need it to improve the behavior related to #13993 (comment)
@RomanNikitenko RomanNikitenko added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Aug 19, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Aug 19, 2019
@sleshchenko sleshchenko added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Aug 20, 2019
@sleshchenko sleshchenko added this to the 7.1.0 milestone Aug 20, 2019
@sleshchenko
Copy link
Member

Is triaged in the same way as depending issue #13993 (comment)

@RomanNikitenko RomanNikitenko mentioned this issue Aug 23, 2019
Closed
@skabashnyuk skabashnyuk modified the milestones: 7.1.0, 7.2.0 Aug 23, 2019
@skabashnyuk skabashnyuk mentioned this issue Sep 4, 2019
Closed
15 tasks
@mshaposhnik mshaposhnik mentioned this issue Sep 20, 2019
Merged
@skabashnyuk skabashnyuk mentioned this issue Sep 25, 2019
Closed
17 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
7.2.0
Development

No branches or pull requests
5 participants
@skabashnyuk @mshaposhnik @RomanNikitenko @sleshchenko @che-bot