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

odo create/delete/list namespace #5525

Closed
8 tasks done
Tracked by #5522
serenamarie125 opened this issue Mar 7, 2022 · 2 comments
Closed
8 tasks done
Tracked by #5522

odo create/delete/list namespace #5525

serenamarie125 opened this issue Mar 7, 2022 · 2 comments
Assignees
Labels
estimated-size/S (5-10) Rough sizing for Epics. Less then one sprint of work for one person kind/user-story An issue of user-story kind

Comments

@serenamarie125
Copy link

serenamarie125 commented Mar 7, 2022

/kind user-story

User Story

  • As an odo user
  • I want to be able to create a namespace (project on OpenShift)
  • So that I can better organize and isolate my applications.

Acceptance Criteria

  • odo create namespace (odo create namespace #5724 )
  • odo delete namespace (Implement odo delete namespace/project #5743 )
  • odo list namespace (odo list namespace #5729 )
  • odo set namespace - updates currently active namespace/project in kubeconfig (the same as running kubectl config set-context --current --namespace=<namespace> or oc project <myproject> (Implement odo set namespace/project #5744)
    • if odo set namespace is executed inside component directory, it should show warning, that this won't update the namespace of the existing component.
  • every namespace command should also be aliased as a project (odo create/delete/list/set project)
  • project/namespace commands should be smart and work on both Kubernetes and Openshift, for example odo create namespace running against OpenShift project will create project, similarly it should be possible to run odo create project on Kubernetes (in this case it will create namespace)
  • odo create/delete/list/set -h should mention that project is OpenShift specific and it alias to namespace
@serenamarie125 serenamarie125 added kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks v3 labels Mar 7, 2022
@serenamarie125 serenamarie125 added this to the v3.0.0-alpha2 milestone Mar 7, 2022
@serenamarie125 serenamarie125 mentioned this issue Mar 7, 2022
20 tasks
@kadel kadel mentioned this issue Mar 7, 2022
4 tasks
@kadel kadel added the triage/needs-information Indicates an issue needs more information in order to work on it. label Mar 22, 2022
@kadel kadel removed the v3 label Mar 24, 2022
@kadel kadel added kind/user-story An issue of user-story kind estimated-size/S (5-10) Rough sizing for Epics. Less then one sprint of work for one person and removed triage/needs-information Indicates an issue needs more information in order to work on it. kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks labels Apr 4, 2022
@kadel kadel moved this to Todo in odo v3-beta1 Apr 27, 2022
@valaparthvi valaparthvi mentioned this issue May 9, 2022
3 tasks
@valaparthvi valaparthvi moved this from Todo to In Progress in odo v3-beta1 May 10, 2022
@valaparthvi valaparthvi mentioned this issue May 11, 2022
3 tasks
@valaparthvi
Copy link
Contributor

@kadel @joshira-rh I am halfway with this issue, I think I can complete it once I'm back. If we're in hurry, I do not mind if someone else wants to pick this up.

@rm3l
Copy link
Member

rm3l commented May 13, 2022

@kadel @joshira-rh I am halfway with this issue, I think I can complete it once I'm back. If we're in hurry, I do not mind if someone else wants to pick this up.

As I am waiting for some feedback on #5648, I think I can continue your work on this issue.

@rm3l rm3l self-assigned this May 16, 2022
@kadel kadel closed this as completed Jun 1, 2022
Repository owner moved this from In Progress to Done in odo v3-beta1 Jun 1, 2022
@rm3l rm3l added the v3 label Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
estimated-size/S (5-10) Rough sizing for Epics. Less then one sprint of work for one person kind/user-story An issue of user-story kind
Projects
No open projects
Status: Done
Development

No branches or pull requests

4 participants