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

fix: don't watch project-level log files #477

Merged
merged 1 commit into from
Jan 25, 2019
Merged

Conversation

thsig
Copy link
Collaborator

@thsig thsig commented Jan 24, 2019

Added *.log to the list of path patterns ignored by default.

Previously, running garden get status in a project where

  • Another Garden command is running in watch mode, and

  • A service from a module at the project level (i.e. with its
    module config in the project-wide garden.yml) is deployed
    with hot reloading enabled,

would erroneously trigger a hot reload of that service, due to the
project-level error.log getting touched during the execution of
garden get status.

Fixes #387.

Added *.log to the list of path patterns ignored by default.

Previously, running `garden get status` in a project where

* Another Garden command is running in watch mode, and

* A service from a module at the project level (i.e. with its
module config in the project-wide `garden.yml`) is deployed
with hot reloading enabled,

would erroneously trigger a hot reload of that service, due to the
project-level `error.log` getting touched during the execution of
`garden get status`.

Fixes #387.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants