theforeman / theforeman/puppet-pulpcore
Improve collectstatic handling
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2
- Forks
- 36
- Avg merge
- 4h 23m
- Merged PRs (30d)
- 1
Description
There's currently a collectstatic job:
This is refreshonly and uses the settings file, but doesn't refresh on it. There may also be other reasons to explicitly trigger it. For example when a yum update happens outside of its control.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with manifests/config.pp at lines 23-30 and inspect how the collectstatic job is configured and triggered. Determine the required refresh conditions described in the issue, including settings changes and yum updates, and verify that the job responds to those events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100