odo deploy --dry-run

[valaparthvi]

/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]

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]

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

[rm3l]

Still relevant.

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