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.

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

Add preStart, preStop and postStop lifecycle event support #3569

Closed
1 task
elsony opened this issue Jul 14, 2020 · 2 comments
Closed
1 task

Add preStart, preStop and postStop lifecycle event support #3569

elsony opened this issue Jul 14, 2020 · 2 comments
Assignees
Labels
area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. kind/user-story An issue of user-story kind

Comments

@elsony
Copy link

elsony commented Jul 14, 2020

/kind user-story

User Story

As a stack creator, I want to make use of the preStart, preStop and postStop events defined in the devfile 2.0.
Devfile 2.0 providers ability to execute commands based on lifecycle events.

Overall design of how to handle those lifecycle events is defined in #3413.

Acceptance Criteria

Links

/kind user-story
/area devfile

@openshift-ci-robot openshift-ci-robot added kind/user-story An issue of user-story kind area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. labels Jul 14, 2020
@neeraj-laad
Copy link
Contributor

@elsony There are separate issue for each of these events too.. Looks @upLukeWeston created them while you had created a common one for this too.

We should close this or close the other three.

#3565
#3566
#3577

@elsony
Copy link
Author

elsony commented Jul 21, 2020

Closing off this one since the 3 events will be implemented separately via #3565, #3566 and #3577

@elsony elsony closed this as completed Jul 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. kind/user-story An issue of user-story kind
Projects
None yet
Development

No branches or pull requests

4 participants