puppetlabs / puppetlabs/puppetlabs-apache
Add ability to support Location not via custom blocks
Nobody has claimed this yet.
- Dominant language
- Puppet
- Stars
- 356
- Forks
- 1.1k
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
Use Case
I was trying to configure reverse proxy and found that there is not possible to create location directives not via custom blocks.
Describe the Solution You Would Like
Add ability to manage locations via puppet and hiera directly.
Describe Alternatives You've Considered
Templating of full vhost configuration is not so good solution.
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 by reviewing how the module currently represents Apache custom blocks and how Puppet and Hiera values reach vhost configuration. Trace the reverse-proxy and location-directive handling, then define how directly managed locations should be configured without full-vhost templating. Done means a working Puppet/Hiera configuration path for locations, with coverage for the requested reverse-proxy use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100