These keystore files would normally be included in a cba archive, most likely in the Environments folder. Yet the blueprint must have an absolute path to the keystore, making it non future proof.
This forces the user to enter a full path mapped in the /opt/onap/ mount point as it is the know location of the cba, once deployed.
But this configuration could change, during deployments.
It would be more useful to have the property evaluated, relative to the cba root dir, so something like Environments/keystore.jks would be supported.
"dsl_definitions" : { "remote-endpoint" : { "type" : "ssl-token-auth", "url" : "https://172.162.152.142", "tokenAuth" :
{ "get_input" : "token" }, "keyStoreInstance" : "JKS", "sslTrust" : "/opt/app/onap/blueprints/deploy/operations/1.0.0/Environments/keystore.jks", "sslTrustPassword" :
{ "get_input" : "password" }, "sslTrustIgnoreHostname": "true" } },