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

new odo workflow: handle env in odo config #1390

Closed
kadel opened this issue Feb 27, 2019 · 0 comments · Fixed by #1562
Closed

new odo workflow: handle env in odo config #1390

kadel opened this issue Feb 27, 2019 · 0 comments · Fixed by #1562
Assignees
Labels
estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
Milestone

Comments

@kadel
Copy link
Member

kadel commented Feb 27, 2019

odo config command needs to handle the environment configs

odo config set --env foo=bar

this will set envrionment foo to value bar

all odo config commands (set, unset, view) needs work with --env flag

@kadel kadel added priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). size/M labels Feb 27, 2019
@girishramnani girishramnani added the status/blocked Denotes an issue or PR that is blocked on something (e.g., issue/PR in different repo) label Mar 5, 2019
@kadel kadel added this to the 1.0 beta1 milestone Mar 20, 2019
@kadel kadel assigned girishramnani and unassigned girishramnani Mar 21, 2019
@kadel kadel removed priority/Medium Nice to have issue. Getting it done before priority changes would be great. labels Mar 26, 2019
@kadel kadel removed status/blocked Denotes an issue or PR that is blocked on something (e.g., issue/PR in different repo) labels Apr 3, 2019
@rm3l rm3l added the estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person label Jun 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants