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

Support expensive services that don't persist #76

Open
1 task done
sichapman opened this issue Jan 9, 2020 · 0 comments
Open
1 task done

Support expensive services that don't persist #76

sichapman opened this issue Jan 9, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@sichapman
Copy link
Collaborator

  • I'm submitting a ...

    • feature request
  • What is the current behavior?
    If you have an expensive service that should have staggered startup, but also is a one off job that exits cleanly, there is no healthcheck to exec successfully so the dev env polls forever

  • What is the expected/proposed behavior?
    Support some way for the expensive service configuration to allow for exit checks (and exit code?)

  • What is the motivation / use case for changing the behavior?
    Support more varied apps

@sichapman sichapman added the enhancement New feature or request label Jan 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant