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

(IAC-1186) Add $use_port_for_filenames parameter #2122

Merged
merged 2 commits into from
Feb 15, 2021

Conversation

smortex
Copy link
Collaborator

@smortex smortex commented Feb 13, 2021

When using $use_servername_for_filenames = true, virtual hosts with the
same $servername but a different $port will introduce a duplicate
resource declaration.

Introduce a $use_port_for_filenames that act in concert with
$use_servername_for_filenames to avoid this situation.

When using $use_servername_for_filenames = true, virtual hosts with the
same $servername but a different $port will introduce a duplicate
resource declaration.

Introduce a $use_port_for_filenames that act in concert with
$use_servername_for_filenames to avoid this situation.
@smortex smortex requested a review from a team as a code owner February 13, 2021 03:46
@puppet-community-rangefinder
Copy link

apache is a class

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

apache::vhost is a type

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

This module is declared in 175 of 576 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.

@smortex
Copy link
Collaborator Author

smortex commented Feb 13, 2021

This is a follow-up to #2086, so ping @sanfrancrisko and @sheenaajay who worked on this previous PR and @DavidS who proposed this change in IAC-1186.

@codecov-io
Copy link

codecov-io commented Feb 13, 2021

Codecov Report

Merging #2122 (fb2a84f) into main (13f55bd) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #2122   +/-   ##
=======================================
  Coverage   56.36%   56.36%           
=======================================
  Files          12       12           
  Lines         220      220           
=======================================
  Hits          124      124           
  Misses         96       96           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c1a830b...fb2a84f. Read the comment docs.

@smortex smortex force-pushed the use_port_for_filenames branch 2 times, most recently from 2612306 to 352f9f2 Compare February 13, 2021 18:02
Copy link
Contributor

@sanfrancrisko sanfrancrisko left a comment

Choose a reason for hiding this comment

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

Apologies, I was a bit less involved in the conversation on IAC-1186 than I wanted to (was out on training most of last week).

Thanks for getting the enhancement up 👍

@sanfrancrisko sanfrancrisko merged commit f1ad00d into puppetlabs:main Feb 15, 2021
@smortex smortex deleted the use_port_for_filenames branch February 15, 2021 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants