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

odo dev --dry-run #5243

Closed
feloy opened this issue Nov 23, 2021 · 3 comments
Closed

odo dev --dry-run #5243

feloy opened this issue Nov 23, 2021 · 3 comments
Labels
area/dev Issues or PRs related to `odo dev` kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/Medium Nice to have issue. Getting it done before priority changes would be great.

Comments

@feloy
Copy link
Contributor

feloy commented Nov 23, 2021 •
edited by valaparthvi

/kind feature

Which functionality do you think we should add?

odo dev --dry-run

These commands should describe which Kubernetes components would be applied in both cases.

Why is this needed?

It can be confusing for a user that a Kubernetes component is sometimes deployed with odo push, and sometimes during odo deploy, depending on if the component is referenced or not from an Apply command.
@openshift-ci openshift-ci bot added the kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation label Nov 23, 2021
@kadel kadel changed the title odo push/deploy --dry-run odo dev/deploy --dry-run Mar 15, 2022
@kadel kadel added the priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). label Mar 15, 2022
@kadel kadel removed the priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). label Sep 9, 2022
@valaparthvi
Copy link
Member

  • Output the K8s YAML that can be directly used by other tools such as kubectl.
  • Do not build the images, for now.

@valaparthvi valaparthvi changed the title odo dev/deploy --dry-run odo dev --dry-run Oct 20, 2022
@valaparthvi valaparthvi mentioned this issue Oct 20, 2022
Open
2 tasks
@kadel kadel added priority/Medium Nice to have issue. Getting it done before priority changes would be great. area/dev Issues or PRs related to `odo dev` labels Feb 8, 2023
@rm3l rm3l mentioned this issue Jun 15, 2023
Open
3 tasks
@github-actions
Copy link
Contributor

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 31, 2023
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Dec 1, 2023

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Dec 1, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/dev Issues or PRs related to `odo dev` kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/Medium Nice to have issue. Getting it done before priority changes would be great.
Projects
odo Project
Archived in project
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kadel @feloy @valaparthvi