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

RPM packaging should use config.d by default #1660

Open
2 of 7 tasks
brianhlin opened this issue Oct 17, 2024 · 0 comments · May be fixed by #1666
Open
2 of 7 tasks

RPM packaging should use config.d by default #1660

brianhlin opened this issue Oct 17, 2024 · 0 comments · May be fixed by #1666
Labels
enhancement New feature or request

Comments

@brianhlin
Copy link
Contributor

Pelican Service:

  • Client
  • Plugin
  • Registry
  • Director
  • Origin
  • Cache
  • Other (please give the detail)

Is your feature request related to a problem? Please describe.

Ahead of the OSG 24 upgrade, we should settle on a more admin-friendly configuration layout using multiple config.d dirs

Describe the solution you'd like

  • Treat /etc/pelican/pelican.yaml as the entrypoint. Should be marked as config but will be overwritten by package updates
  • Create /usr/share/pelican/config.d: this is where default config will go and any edits will be destroyed upon package update
  • Create /etc/pelican/config.d: this is where admin config will go, which will remain untouched by packaging. It's a good location for providing default, commented-out example configurations as long as they're marked config,noreplace
@brianhlin brianhlin added the enhancement New feature or request label Oct 17, 2024
@brianhlin brianhlin linked a pull request Oct 18, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant