[drift] Consider alternative configuration besides driftignore file
Open
enhancement
- Dominant language
- Go
- Stars
- 26
- Forks
- 7
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
### TL;DR
The `driftignore` file is ok for describing a uniform list of assets to ignore but not good at describing complex rules such as
* Skip this project
* Skip this folder and all dependencies
* Skip this folder but not dependencies of it
We should consider moving to a yaml/json `driftconfig` configuration to allow for more complex configuration
NOTE: possibly still consider allowing a `driftignore` for the uniform list of assets? This would mean having both a `driftignore` and `driftconfig`.
### Detailed design
_No response_
### Alternatives considered
_No response_
### Additional information
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.