Open marde16 opened 11 months ago
The setup_invite_config tasks already use a variable for the ldap guid called ldap_guid_field( and there is a ldaps port called ldap_ssl_port )
ldap_guid_field
ldap_ssl_port
Unfortunately these variables aren't documented in the variables overview - why I defined ldap_map_guid variable in my PR ( #293 )
ldap_map_guid
https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/97eb462cd579cbb2f8accb63e22c7e81e5e3bcc4/roles/third_party/ibm/tdi-install/vars/main.yml#L70-L71
In my opinion here it needs some steps for a standardization:
add var __ldap_ssl_port to vars
__ldap_ssl_port
__ldap_ssl_port: "{{ (ldap_ssl_port | default('636')) }}"
and replace ldap_ssl_port | default('636') with __ldap_ssl_port
ldap_ssl_port | default('636')
https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/97eb462cd579cbb2f8accb63e22c7e81e5e3bcc4/roles/hcl/connections/post_install_config/tasks/setup_invite_config.yml#L43
add var __ldap_map_guid to vars
__ldap_map_guid
__ldap_map_guid: "{{ ldap_map_guid | default('entryUUID') }}"
and replace ldap_guid_field | default('entryUUID') with __ldap_map_guid
ldap_guid_field | default('entryUUID')
https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/97eb462cd579cbb2f8accb63e22c7e81e5e3bcc4/roles/hcl/connections/post_install_config/tasks/setup_invite_config.yml#L55
https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/97eb462cd579cbb2f8accb63e22c7e81e5e3bcc4/roles/hcl/connections/post_install_config/tasks/setup_invite_config.yml#L63
replace ldap_guid_field | default('entryUUID') with __ldap_map_guid
finally update missing vars in variable overview page
... and the variable ldap_ssl_port can be used in the issue " LDAP ports hardcoded #276 ", too.
The setup_invite_config tasks already use a variable for the ldap guid called
ldap_guid_field
( and there is a ldaps port calledldap_ssl_port
)Unfortunately these variables aren't documented in the variables overview - why I defined
ldap_map_guid
variable in my PR ( #293 )https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/97eb462cd579cbb2f8accb63e22c7e81e5e3bcc4/roles/third_party/ibm/tdi-install/vars/main.yml#L70-L71
In my opinion here it needs some steps for a standardization:
add var
__ldap_ssl_port
to vars__ldap_ssl_port: "{{ (ldap_ssl_port | default('636')) }}"
and replace
ldap_ssl_port | default('636')
with__ldap_ssl_port
https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/97eb462cd579cbb2f8accb63e22c7e81e5e3bcc4/roles/hcl/connections/post_install_config/tasks/setup_invite_config.yml#L43
add var
__ldap_map_guid
to vars__ldap_map_guid: "{{ ldap_map_guid | default('entryUUID') }}"
and replace
ldap_guid_field | default('entryUUID')
with__ldap_map_guid
https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/97eb462cd579cbb2f8accb63e22c7e81e5e3bcc4/roles/hcl/connections/post_install_config/tasks/setup_invite_config.yml#L55
https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/97eb462cd579cbb2f8accb63e22c7e81e5e3bcc4/roles/hcl/connections/post_install_config/tasks/setup_invite_config.yml#L63
replace
ldap_guid_field | default('entryUUID')
with__ldap_map_guid
https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/97eb462cd579cbb2f8accb63e22c7e81e5e3bcc4/roles/hcl/connections/post_install_config/tasks/setup_invite_config.yml#L55
https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/97eb462cd579cbb2f8accb63e22c7e81e5e3bcc4/roles/hcl/connections/post_install_config/tasks/setup_invite_config.yml#L63
finally update missing vars in variable overview page
... and the variable
ldap_ssl_port
can be used in the issue " LDAP ports hardcoded #276 ", too.