Skip to content

Propagate special error on configuration change #2501

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

Merged
merged 1 commit into from
Jul 19, 2019

Conversation

nkubala
Copy link
Contributor

@nkubala nkubala commented Jul 19, 2019

this change makes sure the special case error for a change to the skaffold.yaml makes its way out of the dev loop and up to the caller, which in turn creates a new runner and kicks off a new dev loop.

Fixes #2500

@codecov
Copy link

codecov bot commented Jul 19, 2019

Codecov Report

Merging #2501 into master will decrease coverage by 0.01%.
The diff coverage is 0%.

Impacted Files Coverage Δ
pkg/skaffold/runner/listen.go 0% <0%> (ø) ⬆️

@balopat
Copy link
Contributor

balopat commented Jul 19, 2019

Great, thank you! Can we have a test around it?

@nkubala nkubala merged commit fe56831 into GoogleContainerTools:master Jul 19, 2019
@nkubala nkubala deleted the reload-config branch July 19, 2019 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ERRO[0033] error running dev loop: configuration changed
3 participants