GoogleContainerTools / GoogleContainerTools/skaffold
Feature Request: Allow configuration so that post deploy hooks can execute after port-forwarding
Open
area/hooks
kind/feature-request
priority/p3
- Dominant language
- Go
- Stars
- 15.9k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 10
Description
As it currently exists, Skaffold will perform the port-forwarding after the post-deploy hook has executed. This doesn't allows us to run any commands that can directly interact the services since port-forwarding hasn't taken place. Currently, we are forced into a situation where we have written a "wrapper" around the skaffold executable so that we can execute the commands as a single lifecycle for local dev and CI/CD pipelines.
My team would like an option where we can specify whether post-deploy hooks should happen before or after port-forwarding
Contributor guide
Assessment
This issue has not been assessed yet.