You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our Python projects it is a common pattern to have two requirements files:
requirements.txt to declare dependencies which get bundled with our code and installed in productive systems
dev-requirements.txt to declare development and CI dependencies which are needed to build and test the code but are not required for productive runtime configurations.
We explicitly have these two files to separate tools such as sphinx and ansible which have licenses that allow development use but we do not want to link within our code or "distribute" with our products.
I can't find a way to have the FOSSA configuration ignore an individual file. If I specify paths.exclude: dev-requirements.txt in .fossa.yml or other mechanisms it is ignored. I believe these configs only work at a directory level.
At this time I'm forced to delete the dev-requirements.txt from the root directory before fossa analyze which is undesirable.
Can we allow excludes at a file level to support this use case?
I believe that having requirements files for each environment (dev,test,prod) is fairly common. Licensing implications is one reason why.
The text was updated successfully, but these errors were encountered:
You are correct that the paths.exclude filter will not work for this, as it only filters at the directory level.
We have had a feature request in our backlog for turning the various *req*.txt files into subtargets, so that they can be used with targets.exclude or targets.only:
agree with you @chrisfarnham , I really desperate looking for a way to exclude a specific file, instead of directory only.
And @scruffystuffs , I'd really hope fossa could support this feature just like the directories, I mean I could simply add another item in .fossa.yml.
In our Python projects it is a common pattern to have two requirements files:
We explicitly have these two files to separate tools such as sphinx and ansible which have licenses that allow development use but we do not want to link within our code or "distribute" with our products.
I can't find a way to have the FOSSA configuration ignore an individual file. If I specify paths.exclude: dev-requirements.txt in .fossa.yml or other mechanisms it is ignored. I believe these configs only work at a directory level.
At this time I'm forced to delete the dev-requirements.txt from the root directory before fossa analyze which is undesirable.
Can we allow excludes at a file level to support this use case?
I believe that having requirements files for each environment (dev,test,prod) is fairly common. Licensing implications is one reason why.
The text was updated successfully, but these errors were encountered: