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

Enable subdirectory hierarchy for client_body and proxy temp paths #1531

Merged
merged 1 commit into from
Jan 3, 2023

Conversation

jplindquist
Copy link
Contributor

Pull Request (PR) description

Allow specification of up to three-level subdirectory hierarchy for both client_body_temp_path and proxy_temp_path options

This allows for the existing string option to specify just the path as it works now, and for an alternate type as an array with the first element as the path, and the up to 3 additional integers for each level

  • Updated docs
  • Updated tests

@puppet-community-rangefinder
Copy link

nginx::config is a class

Breaking changes to this file MAY impact these 2 modules (near match):

nginx is a class

Breaking changes to this file WILL impact these 16 modules (exact match):
Breaking changes to this file MAY impact these 33 modules (near match):

This module is declared in 9 of 580 indexed public Puppetfiles.


These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

@jcpunk
Copy link

jcpunk commented Jan 3, 2023

Neat! Looks good to me, but I'll defer to folks with more experience on this module.

Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some trivial nits, but overall I think this looks valid. I'm not that familiar with the config option so say if this is useful or usable.

manifests/config.pp Outdated Show resolved Hide resolved
spec/classes/nginx_spec.rb Outdated Show resolved Hide resolved
@jplindquist
Copy link
Contributor Author

Thank you @ekohl , updated!

@jcpunk
Copy link

jcpunk commented Jan 3, 2023

I'd love to see this squashed down to one commit.

Allow specification of up to three-level subdirectory hierarchy for
both [client_body_temp_path](https://nginx.org/en/docs/http/ngx_http_core_module.html#client_body_temp_path)
and [proxy_temp_path](https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_temp_path) options

This allows for the existing string option to specify just the path as
it works now, and for an alternate type as an array with the first
element as the path, and the up to 3 additional integers for each level

- Updated docs
- Updated tests

Rubocop fix

Apply suggestions from code review

Co-authored-by: Ewoud Kohl van Wijngaarden <ewoud@kohlvanwijngaarden.nl>

Rubocop suggested fix
@bastelfreak bastelfreak added the enhancement New feature or request label Jan 3, 2023
@bastelfreak bastelfreak merged commit 5b294a2 into voxpupuli:master Jan 3, 2023
@jplindquist jplindquist deleted the temp_path_depth branch January 3, 2023 18:03
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 this pull request may close these issues.

4 participants