-
Notifications
You must be signed in to change notification settings - Fork 224
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
Feature: "watch" mode -> automatic build/push/deploy on save #472
Comments
I was chatting to @johnmccabe about this, we're thinking of adding |
@johnmccabe how did the initial attempt go with this? How does Docker-Compose handle de-bounce? |
Initial PoC worked well, I'll pick this up after work tomorrow and get something pushed up for eyeballs. |
Awesome John. |
@johnmccabe do you still have work in progress for this? |
Yeah, needs dusted off and pushed (got side-tracked helping with the minikube stuff) - I can swing back round to this on Sunday after I get VMUG and PHP Scotland out of the way. |
Do you still have a local copy? Anything we should be aware of or watch for? |
Expected Behaviour
New feature: file-system watch mode will detect a change in a function handler folder and then automatically build/push/deploy the affected function.
This would be done via the existing OpenFaaS API meaning all backends are supported - faas-fargate, faas-swarm, faas-netes and openfaas-operator.
Similar things are done in entire projects such as skaffold from Google. I know Stefan @stefanprodan is a fan of this project. I believe Skaffold needs a Dockerfile in a set place, we can workaround this by using "faas-cli build --shrinkwrap" or maybe a combination of all of the above.
The basic idea is to allow a "watch" / auto-reloader experience for function development.
Thoughts?
The text was updated successfully, but these errors were encountered: