Make some of the j2 templates source configurable #296
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.
For some custom/advanced setups it would be nice if we could customize some of the default provided templates. It is the case of
motd.j2
template from the common role,sudoers.j2
from the orahost role (if for example I don't want NOPASSWD for sudo or I'd like access to a few commands only) anddotprofile-home.j2
from oraswdb-install role. With the proposed changes I can create for example my owndotprofile-home.j2
, place it in my templates/ folder in the root of my playbook directory and setoracle_profile_template
to"{{ playbook_dir }}/templates/dotprofile-home.j2"
. I can do all these manually through some post_tasks, of course, but it would unnecessarily complicate the playbook. Not to mention that generating dotprofile file can't be currently disabled. This patch adds also a newconfigure_oracle_profile
variable to control whether the profile file should be generated.