What would you like to be added:
The ability for "excludeFiles:" to work with "manifest" in the same way it currently does with "fileTree", in order to allow for maximum reuse of manifest files across repositories.
Why is this needed / describe a real-world scenario:
Adding an entire manifest through docforge is an incredibly useful tool, allowing for reuse of both content and structure without the need for double maintenance. However, in certain use cases you might not want to take the contents of an entire manifest file:
- You have a modified version of a file already existing, so you don't want to also copy over the original/public file
- You want to reuse an existing manifest file, but do not need its entire content
I such cases, the ability to exclude certain files or paths from the manifest would be helpful and allow to reuse content with greater ease.
How to categorize this?:
/kind enhancement
/priority 3
What would you like to be added:
The ability for "excludeFiles:" to work with "manifest" in the same way it currently does with "fileTree", in order to allow for maximum reuse of manifest files across repositories.
Why is this needed / describe a real-world scenario:
Adding an entire manifest through docforge is an incredibly useful tool, allowing for reuse of both content and structure without the need for double maintenance. However, in certain use cases you might not want to take the contents of an entire manifest file:
I such cases, the ability to exclude certain files or paths from the manifest would be helpful and allow to reuse content with greater ease.
How to categorize this?:
/kind enhancement
/priority 3