You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 27, 2023. It is now read-only.
Need to discuss, if the role should be splitted in media-check, user-management, installation and license. Currently this role does all of it, but I think we shoul revisit this for sake of simplicity, i.e.
Customers do have there Hana versions unpacked in NFS or CIFS shares
Customers may have users and groups predefined in corporate directories
the role can currently either install OR set the license not both, so why not two roles?
The text was updated successfully, but these errors were encountered:
@rhmk One problem if we split the role into 3 or 4 separate roles is that we will create some complexity in other areas like different variable name prefixes, different README files, ..., although they all related to the SAP HANA installation.
Regarding your first topic: For customers which have their HANA software already unpacked in NFS or CIFS shares, the current version of the role is probably sufficient as it can be configured without setting the SAP HANA bundle/zip file names and will then install from sap_hana_installdir.
Regarding the second topic, is it already solved because the HANA user and group IDs can be set in the role?
Regarding your last topic: In #40, I am showing a simple solution for your last point.
Need to discuss, if the role should be splitted in media-check, user-management, installation and license. Currently this role does all of it, but I think we shoul revisit this for sake of simplicity, i.e.
The text was updated successfully, but these errors were encountered: