-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
mod_auth_gssapi: Add support for every configuration directive #2214
Conversation
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.
@canth1 Hey, sorry for the wait on review.
Anyway, while this look's like a great change and an excellent addition of functionality it is causing some unit test failures seeming to originate from the new acceptor_name value.
If you could get this solved I would be happy to merge, I've included an example of the error below:
Failures:
1) apache::vhost os-independent items on oraclelinux-6-x86_64 set everything! is expected to compile into a catalogue without dependency cycles
Failure/Error: acceptor_name => '{HOSTNAME}',
NameError:
undefined local variable or method `acceptor_name' for #<RSpec::ExampleGroups::ApacheVhost::OsIndependentItems::OnOraclelinux6X8664::SetEverything:0x00005576c6b33570>
# ./spec/defines/vhost_spec.rb:255:in `block (6 levels) in <top (required)>'
# ./spec/defines/vhost_spec.rb:531:in `block (6 levels) in <top (required)>'
# ./vendor/bundle/ruby/2.5.0/bin/rspec:23:in `load'
# ./vendor/bundle/ruby/2.5.0/bin/rspec:23:in `<top (required)>'
# ./vendor/bundle/ruby/2.5.0/bin/bundle:23:in `load'
# ./vendor/bundle/ruby/2.5.0/bin/bundle:23:in `<main>'
@canth1 Sorry to come back but while reviewing your pr I noticed that a similar change had been pushed up by another contributor that contains part of the functionality that you yourself have added. Just felt I should alert you as depending on which PR is merged first you may need to rebase your work. |
In relation to the comment above, have discovered two more PRs that are adding similar functionality to this, one of which was in a good enough state to be merged: And another which will require some more work: |
Thanks for the update on this. I'll work on getting those issues fixed. As far as the other pull requests, I would argue that you should use this one as it is a complete implementation of every mod_auth_gssapi configuration option. From what I've seen, the other pull requests only add a few additional options, leaving the functionality incomplete. |
Looking at this closer, is the issue that the { and } aren't escaped correctly in the vhost_spec.rb file? |
I don't think so, from the way the error is presented it seem's to come from where the acceptor_name is being set. |
Reading through the errorlogs see a lot of:
|
@canth1 Is this still something you plan to work on? |
I really do, but from everything I've looked at I can't figure out what's throwing that error. Is it possible that it's a false positive? |
@canth1 Took a look at your failure and found what was causing it, basically you need to put your test values in strings, they don't mock correctly if just passed in naked, i.e. include them as:
Sorry it took me so long to remember the test limitation, but if you fix this and rebase then your pr to resolve the conflicts should be good to merge. |
Ok, I've updated the vhost_spec.rb and the issue should be fixed. Let me know if you need anything else from me! |
@canth1 Just one more change sorry. |
Ok, I just fixed those conflicts. |
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
@canth1 Ok that's that then, sorry for asking for so many changes but it all looks good now so I'm gonna go ahead and merge. |
Of course. I use this Puppet module extensively, so I'm glad that I'm able to contribute back to it. Thanks again! |
This allows every configuration directive available to mod_auth_gssapi to be configured inside a directory section of a vhost.
Example
The above config results in an Apache configuration of: