-
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
Allow custom library paths and module identifier names #97
Conversation
This changeset will allow users to set custom module identifier string similar to module package name and module library name. For example, module identifier string for shibboleth can be set as: $mod_identifiers = { 'shibboleth' => 'mod_shib', } See github #1 for details.
See github #2 for details. Allowed user to specify custom module library .so file location using an absolute path. If the module library location string starts with a forward slash '/', then the path is taken as an absolute path. Otherwise, a relative path from default 'modules' directory is taken.
Thanks! I +1 this but want a second review. |
|
||
# Set libfile path: If absolute path is passed then maintain it, else make it default 'modules/module-name' | ||
def libfile | ||
abs_path_regex = /^\/.*/ |
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.
Ruby has functions for checking if a path is absolute. That would be much clearer than a hand-rolled regex here
Thanks for the suggestion @branan. Updated code to use Ruby's pathname library for absolute/relative path check. Also, added module identifier parameter to a2mod resource and default parameters list. |
ping |
Right! Thanks for pinging. |
Allow custom library paths and module identifier names
docker::registry fixes
Mentioned below are two commits in this pull-request:
Any comments or questions are welcome.