Comment 14 for bug 1612204

Alex,
"Everything that is done is done for the best".

I re-reviewed all Heat code again + patch and unfortunately for me need to say,
that we should not change it.
This options also changes parameter for internal clients, that is not security safe way.
So generally you are right.

However all words about wait condition curl are true.
>> Where is the curl command ultimately run and are we not publishing the self signed CA everywhere?

This curl request will be executed in VM, which will be launched in Heat stack, i.e. usual VM booted by Nova. So issue here, that user should put certificate for Openstack inside his custom/own VM. Obviously He has not this certificate - because it's not security safe too.

I thought, that it's good solution for us, but unfortunately it just re-use existing "insecure" option, which is not what we want to have.

We will fix tests.