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 jinja search path for local file_client #18860

Merged
merged 2 commits into from
Dec 11, 2014

Conversation

terminalmage
Copy link
Contributor

This is a re-opening of #18792, which was merged by accident. It has some
test failures that need to be resolved before it is merged.

Now that FS backends other than roots work with a local file_client, there is
no need to look only in the file_roots directories.

Fixes #17963.

Now that FS backends other than roots work with a local file_client,
there is no need to look only in the file_roots directories.

Fixes saltstack#17963.
@ghost
Copy link

ghost commented Dec 9, 2014

Test Failed.

If the failures are unrelated to your code, don't stress, a core developer will know these apart.
In the future, if possible, please branch off a passing commit to avoid false positives.
Refer to this link for build results: http://jenkins.saltstack.com/job/salt-pr-build/11200/

These tests were using the now-outdated method of looking in the
file_roots for cached templates in masterless mode.
@terminalmage
Copy link
Contributor Author

The tests should now be fixed, waiting on Jenkins results.

@ghost
Copy link

ghost commented Dec 11, 2014

Test PASSed.
Refer to this link for build results: http://jenkins.saltstack.com/job/salt-pr-build/11262/

thatch45 added a commit that referenced this pull request Dec 11, 2014
Fix jinja search path for local file_client
@thatch45 thatch45 merged commit 43b307f into saltstack:2014.7 Dec 11, 2014
@terminalmage terminalmage deleted the issue17963 branch February 23, 2015 15:25
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