HorizonSecureCookies is incompatible with non-ssl deployments

[Ben Nemec]

But it is currently turned on by default, which breaks horizon in a default deployment. We should default HorizonSecureCookies to false and turn it on in the enable-tls.yaml environment file.

See also https://bugs.launchpad.net/tripleo/+bug/1696439

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/472447

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/472447
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=d8c0c33012d9a75e980f9f6cef59367594258af9
Submitter: Jenkins
Branch: master

commit d8c0c33012d9a75e980f9f6cef59367594258af9
Author: Ben Nemec <email address hidden>
Date: Thu Jun 8 16:28:34 2017 -0500

    Change HorizonSecureCookies default to False

    HorizonSecureCookies is incompatible with non-ssl deployments, which
    is our default deployment method. When SSL is in use, it can be
    turned on in the enable-tls.yaml file. This does mean that
    existing users won't automatically get this feature turned on as
    part of their upgrade because enable-tls.yaml is an environment that
    is intended to be copied and edited, but it's simple to add the
    parameter to the file for users who want that behavior after they
    upgrade to a version where it is available.

    Change-Id: If83d3d8709fc4e0c09569e8bf524721d332bf560
    Closes-Bug: 1696861

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 7.0.0.0b3 development milestone.