Add class to manage security-role in web.xml #86
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To change the
security-role
currently one must editweb.xml
directly, and reapply the change upon upgrade, as that file is version-specific and must be kept in sync with the application. I have opened an issue with rundeck to make that configurable via something in/etc/rundeck
(rundeck/rundeck#1261), but unless or until that is resolved, I need to be able to manage it.This creates a
rundeck::config::global::web
class with this as the sole parameter which is also added and passed throughrundeck
andrundeck::config
. I chose to use an augeas resource because the file is XML and needs to be replaced outside of Puppet, so a template would not work. Many people have an aversion to augeas because it can get complicated; I find that for certain classes of problems it can be fairly easy. The only hitch is that testing augeas commands is non-trivial (requires rspec-puppet-augeas which was broken for a while due to rspec-puppet).I would also like to be able to set the
session-timeout
inweb.xml
so if this approach is acceptable I will add that to the...::web
class.