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

Ability to specify a type as "config|tree" for /etc so that all files are referenced in configfiles #769

Open
2 tasks done
acabarbaye opened this issue Jan 16, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@acabarbaye
Copy link

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

@acabarbaye acabarbaye added the enhancement New feature or request label Jan 16, 2024
@caarlos0 caarlos0 added this to the 2.38.0 milestone May 9, 2024
@ursetto
Copy link

ursetto commented Jun 27, 2024

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.

@caarlos0 caarlos0 modified the milestones: 2.38.0, 2.39.0 Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants