-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Use a stricter data type on apache::vhost::aliases #2253
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
Conversation
@@ -1803,7 +1803,7 @@ | |||
Optional[Array[Hash]] $access_logs = undef, | |||
Boolean $use_servername_for_filenames = false, | |||
Boolean $use_port_for_filenames = false, | |||
Optional[Variant[Array[Hash],Hash,String]] $aliases = undef, | |||
Array[Hash[String[1], String[1]]] $aliases = [], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be even better if we use a Struct to describe the possible keys and enforce that path
is present, but this is good enough for now.
@ekohl Look's like the rubocop failure is still occurring, swapping the position of
|
This also implements a real test on the rendered template. It appears it was passing in something invalid ever since it was introduced in f1d64a0. The test block is moved because Rubocop didn't quite understand it otherwise.
67a35d3
to
a18271b
Compare
Looks like it passes that now. Let's see for the real unit tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Got one transient failure and one setup failure, but happy to merge :) |
This also implements a real test on the rendered template. It appears it was passing in something invalid ever since it was introduced in f1d64a0.