Sean Freeman

@rainerleber Can you please fix this mergeback to `dev` branch? We should be PR'ing all changes `dev`, testing all changes and then when ready to release, PR'ing into `main` and...

Closing this PR for the following reasons: 1. PR is a copy/paste without any integration - to existing Ansible Collection sap_libs for low-level Ansible Modules - to existing Ansible Roles...

@nsolthe Good use case, but there is very limited Oracle DB experience within the core development team, it is unlikely automation of MOPatch will be a priority. For your use...

@berndfinger I am not in favour of creating defaulting "symlink" (kinda) approach between passwords in the long-term; I'd rather have a new Ansible Task `fail:` for any password that is...

@rob0d @remrozk 1. See https://github.com/sap-linuxlab/community.sap_install/issues/747#issuecomment-2238752327 , repeating here for ease "Original code is from PR #446 describing hdbuserstore incorrectly populated by SWPM using the IP Address instead of Hostname" 2....

@remrozk Can you please test whether the following added to `community.sap_install/roles/sap_swpm/tasks/pre_install/password_facts.yml` provides the same behaviour you are looking for? ```yaml - name: SAP SWPM Pre Install - Set fact for...

@remrozk You do not want to remove that Ansible Task, for reason given above (search page for `Original code` keywords). The command in question was updated last week in PR...

While it can be used, is this common to use in new installations and worth doing? The `credentials` block with master password, adm password etc. are the the usual candidates...

@rob0d To be verbose, to facilitate closing this PR I would like to see the following: - the code block in Jinja - appending the parameter in the YAML List...

As described, PR was replaced by PR #874