-
Notifications
You must be signed in to change notification settings - Fork 244
Labels
area/devIssues or PRs related to `odo dev`Issues or PRs related to `odo dev`area/odo-on-podmanIssues or PRs related to running odo against PodmanIssues or PRs related to running odo against Podmankind/user-storyAn issue of user-story kindAn issue of user-story kindpriority/HighImportant issue; should be worked on before any other issues (except priority/Critical issue(s)).Important issue; should be worked on before any other issues (except priority/Critical issue(s)).sprint demoIndicates an issue for which a demo should be recorded and presented at the end of the sprint.Indicates an issue for which a demo should be recorded and presented at the end of the sprint.
Milestone
Description
/kind user-story
User Story
As a user running odo against Podman, I want changes to my Devfile to be detected and applied, So that I can continuously iterate on my project without having to restart odo dev manually.
Restarting odo dev manually every time I edit something in the Devfile can be annoying and time-consuming.
Currently, it detects any changes to the Devfile and warns users that odo dev needs to be restarted (see #6336). Even changes that would not affect the running Pod (like changes to the build or run commands) are ignored.
Acceptance Criteria
[ ] It should recreate the Pod on Podman if there are changes in the Devfile that would modify the Pod spec (e.g., changes in the container component, ...)[ ] It should not recreate the Pod on Podman if there are changes in the Devfile that would not modify the Pod spec (e.g., changes to theruncommand only)[ ] Similarly to howodo devworks against a cluster, it should notify users of the current Pod state[ ] Similarly to howodo devworks against a cluster, external factors that might affect the running Pod should also be handled by recreating the Pod if needed (but that can be a separate issue)- For now, it should just recreate the Pod on Podman if there any changes in the Devfile
- Update documentation: remove this point from the "Podman Support limitations" page
Links
- Related Epic (mandatory): [Epic] Use odo with Podman (without Kubernetes/OpenShift cluster) [stage 2] #6578
- Related Issue:
odo devneeds to handle changes indevfile.yaml#5728
/kind user-story
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/devIssues or PRs related to `odo dev`Issues or PRs related to `odo dev`area/odo-on-podmanIssues or PRs related to running odo against PodmanIssues or PRs related to running odo against Podmankind/user-storyAn issue of user-story kindAn issue of user-story kindpriority/HighImportant issue; should be worked on before any other issues (except priority/Critical issue(s)).Important issue; should be worked on before any other issues (except priority/Critical issue(s)).sprint demoIndicates an issue for which a demo should be recorded and presented at the end of the sprint.Indicates an issue for which a demo should be recorded and presented at the end of the sprint.
Type
Projects
Status
Done ✅