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

Undocumented behavior for paths matched by multiple fileglobs #367

Closed
Lambdara opened this issue Feb 16, 2018 · 1 comment
Closed

Undocumented behavior for paths matched by multiple fileglobs #367

Lambdara opened this issue Feb 16, 2018 · 1 comment

Comments

@Lambdara
Copy link

Lambdara commented Feb 16, 2018

When I specify the same path multiple times, it seems to just use the configuration for the first time it was specified. This is undocumented however and I'm not sure if this behavior is consistent and can be relied upon.

This behavior can be useful, for example by specifying one extra field for logs/specific.log and another field for logs/*.log. This would specifcy specific.log two times. This second time just gets igored it seems.

It would be nice to know if this behavior can be relied upon (and if so, I think it should be documented in the specification of the files field), and what the details of this behavior would be.

@driskell
Copy link
Owner

I've now documented that the first matching configuration will be used. Also added to code to enforce this in case of a race where file appears middle of a scan.

In future an option to "exclude" files from a scan would perhaps help but as it stands the way the prospector scans would be significant work to make it support "deferring" configuration until it finishes collecting it together. So I don't have any plan to do that.

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

No branches or pull requests

2 participants