heat-manage script encrypts default parameters

[Pratik Mallya]

If the parameters are specified as default, then they are not sensitive and should not be encrypted. This is because the default parameters are visible and accessible in the raw_template entry for the template.

[OpenStack Infra (hudson-openstack)]

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

[Steve Baker (steve-stevebaker)]

See my review comment

[Pratik Mallya (pratik-mallya)]

This is an invalid bug. See https://bugs.launchpad.net/heat/+bug/1506167

[OpenStack Infra (hudson-openstack)]

Change abandoned by Pratik Mallya (<email address hidden>) on branch: master
Review: https://review.openstack.org/217377

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/242185
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=535744b4ca650bb44cc5e207e68d9ffb9b7c5a3a
Submitter: Jenkins
Branch: master

commit 535744b4ca650bb44cc5e207e68d9ffb9b7c5a3a
Author: Pratik Mallya <email address hidden>
Date: Wed Aug 26 15:26:28 2015 -0500

    Don't encrypt default parameters in heat-manage encrypt script

    If a parameter has a default value, that must mean that its
    not sensitive enough to be hidden. So don't hide it by encryption.

    Change-Id: Iec209ba6f6778f728a7938b2ab1fd8b4c5b69bd0
    Closes-Bug: #1489157
    Closes-Bug: #1488679

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/heat 6.0.0.0rc1 release candidate.