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 deploy --dry-run #6240

Open
2 tasks
valaparthvi opened this issue Oct 20, 2022 · 6 comments
Open
2 tasks

odo deploy --dry-run #6240

valaparthvi opened this issue Oct 20, 2022 · 6 comments
Labels
kind/user-story An issue of user-story kind lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. priority/Medium Nice to have issue. Getting it done before priority changes would be great.

Comments

@valaparthvi
Copy link
Member

valaparthvi commented Oct 20, 2022 •
edited by kadel
Loading

/kind user-story

User Story

  • As an odo user
  • I want to be able to show what resources would be created on the cluster without actually applying them
  • So that I can view what odo will do on my cluster
  • So that I can debug easy problems that I'm facing with variables substitution inside Devfile

Acceptance Criteria

  • odo deploy should have --dry-run that will output all Kubernetes resource formated as YAML separated by --- that would be created on the cluster
  • odo dev should have --dry-run that will output all Kubernetes resources formated as YAML separated by --- that would be created on the cluster. When this flag is specified, the command exists right after printing all the objects (no waiting for anything)

/kind user-story

original text:

Which functionality do you think we should add?

odo deploy --dry-run

The command 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 deploy, depending on if the component is referenced or not from an Apply command.
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Oct 20, 2022
@valaparthvi valaparthvi added kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation and removed needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. labels Oct 20, 2022
@kadel kadel added priority/Medium Nice to have issue. Getting it done before priority changes would be great. kind/user-story An issue of user-story kind and removed kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation labels Mar 9, 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 Jul 22, 2023
@github-actions
Copy link
Contributor

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 Aug 22, 2023
@rm3l
Copy link
Member

rm3l commented Sep 7, 2023

Still relevant.

/remove-lifecycle stale
/remove-lifecycle rotten
/reopen

@rm3l rm3l reopened this Sep 7, 2023
@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 7, 2023
@github-actions github-actions bot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. labels Sep 7, 2023
@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Sep 7, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Oct 8, 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 Oct 8, 2023
@github-actions github-actions bot closed this as completed Oct 8, 2023
@rm3l rm3l removed the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Oct 9, 2023
@rm3l
Copy link
Member

rm3l commented Oct 9, 2023

Still relevant.

/remove-lifecycle stale
/remove-lifecycle rotten
/lifecycle frozen
/reopen

@openshift-ci
Copy link

openshift-ci bot commented Oct 9, 2023

@rm3l: Reopened this issue.

In response to this:

Still relevant.

/remove-lifecycle stale
/remove-lifecycle rotten
/lifecycle frozen
/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot reopened this Oct 9, 2023
@openshift-ci openshift-ci bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Oct 9, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Oct 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/user-story An issue of user-story kind lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. priority/Medium Nice to have issue. Getting it done before priority changes would be great.
Projects
odo Project
Status: No status
Milestone
No milestone
Development

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