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
Is your feature request related to a problem? Please describe.
currently, config type seems to only apply to individual files and according to schema cannot be used in addition to the tree type.
Describe the solution you'd like
the solution would be to introduce a new type config|tree which would combine the behaviour of each type: reproduce the tree structure and mark each files found as configuration file
Describe alternatives you've considered
the only alternative is to do this manually and reference every file as "config".
Search
I did search for other open and closed issues before opening this.
Code of Conduct
I agree to follow this project's Code of Conduct
Additional context
No response
The text was updated successfully, but these errors were encountered:
Just want to note that config|noreplace is practically required for RPM packages -- fpm defaults to %config(noreplace) for all RPM config files -- and so ideally should be supported with this new config|tree option. But since these are types (not flags) under the current implementation, that would result in a combinatorial explosion of types like config|tree|noreplace.
Is your feature request related to a problem? Please describe.
currently,
config
type seems to only apply to individual files and according to schema cannot be used in addition to thetree
type.Describe the solution you'd like
the solution would be to introduce a new type
config|tree
which would combine the behaviour of each type: reproduce the tree structure and mark each files found as configuration fileDescribe alternatives you've considered
the only alternative is to do this manually and reference every file as "config".
Search
Code of Conduct
Additional context
No response
The text was updated successfully, but these errors were encountered: