When deploying OSISM, the population and usage of various files/secrets is hard to follow. Updating specific files might not have a direct impact on the deployment.
As an example: Changing the (in this case faulty) SSH certificates in secrets (e.g. for id_rsa.configuration) after having run the cookiecutter does not improve getting access, in this case to GIT.
SSH certificates are seemingly (at some point in the beginning) populated and encrypted into ../environments/manager/secrets.yml.
Changing the document in secrets does not have an impact at all.
Questions arise, on 1) when (in the deployment process) 2) which files can be changed and actually be populated/used/have an impact.
For 3) which files would be a mechanism required, to modify the files and only through some mechanism, the deployment.
Especially helpful regarding SSH Key population into secrets would be an update mechanism, dedicated to to-be encrypted files.
When deploying OSISM, the population and usage of various files/secrets is hard to follow. Updating specific files might not have a direct impact on the deployment.
As an example: Changing the (in this case faulty) SSH certificates in secrets (e.g. for id_rsa.configuration) after having run the cookiecutter does not improve getting access, in this case to GIT.
SSH certificates are seemingly (at some point in the beginning) populated and encrypted into ../environments/manager/secrets.yml.
Changing the document in secrets does not have an impact at all.
Questions arise, on 1) when (in the deployment process) 2) which files can be changed and actually be populated/used/have an impact.
For 3) which files would be a mechanism required, to modify the files and only through some mechanism, the deployment.
Especially helpful regarding SSH Key population into secrets would be an update mechanism, dedicated to to-be encrypted files.