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

Changed max_fails data type validation to Integer[0] since nginx allo… #1342

Merged
merged 1 commit into from Dec 31, 2019

Conversation

andreasnanko
Copy link

…ws to set max_fails=0 (disables accounting of attempts)

http://nginx.org/en/docs/http/ngx_http_upstream_module.html#max_fails

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

@puppet-community-rangefinder
Copy link

nginx::resource::upstream::member is a type

The enclosing module is declared in 11 of 577 indexed public Puppetfiles.

that may have no external impact to Forge modules.


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.

@bastelfreak bastelfreak added the bug Something isn't working label Dec 31, 2019
@bastelfreak bastelfreak merged commit 11dfef0 into voxpupuli:master Dec 31, 2019
Rubueno pushed a commit to Rubueno/puppet-nginx that referenced this pull request Oct 19, 2020
Changed max_fails data type validation to Integer[0] since nginx allo…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants