-
Sub-task
-
Resolution: Done
-
Medium
-
Frankfurt Release
-
None
-
None
Inventory API currently expects to see a config file with a path to a keystore file and a password for the keystore. The tls-init container does not support this–the tls container provides a keystore file and another file containing the password. For the El Alto release, inventory API used the keystore "baked in" to the DCAE tls-init container and hardcoded the keystore password into the inventory API config file.
Probably inventory API will need to add a script that reads from the password file provided by the tls-init container and edits the inventory api configuration file to insert the password read from the password file.