Comment 2 for bug 1639787

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-tripleoclient (master)

Reviewed: https://review.openstack.org/394419
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=fb6f500ffed3696f2b8cffdb5338ff4aa2bdd12f
Submitter: Jenkins
Branch: master

commit fb6f500ffed3696f2b8cffdb5338ff4aa2bdd12f
Author: Dougal Matthews <email address hidden>
Date: Mon Nov 7 13:12:08 2016 +0000

    Reset the parameter_defaults between deployments via the CLI

    When the CLI makes subsequent deployments it manually updates the plan
    in Mistral. We need to do this for backwards compatibility as the deploy
    command previously didn't have any plans or history behind it. So if a
    user deploys with a specific parameter or template and then they remove
    it in the next deploy it shouldn't still exist. In short, the CLI
    expects everything to be passed to the deploy command every time.
    Therefore, the easiest way to handle this is by manually resetting the
    plan.

    This has mostly been the case, but we neglected to reset the
    parameter_defaults. Meaning, that a user may deploy with a parameter
    like "ComputeScale: 5" and then deploy again, without defining it and it
    would use the previous value when they would expect it to use the
    default.

    Change-Id: I09048a550599146ef9bd81a309d80b10497df7c8
    Closes-Bug: #1639787