odo dev --dry-run #5243
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.
/kind feature
Which functionality do you think we should add?
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 duringodo deploy
, depending on if the component is referenced or not from anApply
command.The text was updated successfully, but these errors were encountered: