-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
(#110) Add support for customizing realm.properties #111
Conversation
What's the advantage of managing the template yourself vs writing the configuration of the template that's already present? |
The reason this sort of pattern appears again and again in modules is mostly due to the fact that the module (this module) does not update the configuration as new versions are released. If we could keep up with the new configuration in rundeck and if we were managing it all as per documentation then this would not be required, however that is unrealistic so it's valid for us to do. Having said all that. This pattern does actually scale to more than a couple of templates so we need to be careful about it's use. |
This pull request (along with 109) unhacks our |
realm.properties is already a pretty generic template. What is it that you are trying to add by using your own? Or it it a UX thing? |
@liamjbennett IMO it's a good idea to be as generic as possible; we can't account for all possibilities of the use of this module. @patcadelina please rebase. |
Ok, will merge this once rebased. |
53401ed
to
64df9db
Compare
Rebased. |
@patcadelina thank you very much for this patch! |
Yep, please go ahead @igalic. |
(#110) Add support for customizing realm.properties
Using
realm_template
,realm.properties
could be customized. By default,rundeck/realm.properties.erb
is used.