commit a75d3c94d8e07a5a73e008925eb6fc25515d7c13
Author: Steven Hardy <email address hidden>
Date: Thu Jun 12 14:18:58 2014 +0100
Allow passing an existing user_creds_id to parser.Stack
Currently we always create a new user_creds entry every time a stack
is stored, even if a user_creds_id is passed to the constructor. So
allow an existing user_creds ID to be respected.
This will enable optimisation of the creation of trusts, e.g so we won't
have to create a new trust for every nested stack, we can pass the top
level credentials into the nested stack instead, which means updates which
create nested stacks with a trust-scoped-token will work.
This will be required for updates via trusts from Solum, and probably
also to make OS::Heat::AutoScalingGroup work with the trust-alarm-urls
blueprint, where ceilometer will send a signal using a trust.
Reviewed: https:/ /review. openstack. org/99729 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=a75d3c94d8e 07a5a73e008925e b6fc25515d7c13
Committed: https:/
Submitter: Jenkins
Branch: master
commit a75d3c94d8e07a5 a73e008925eb6fc 25515d7c13
Author: Steven Hardy <email address hidden>
Date: Thu Jun 12 14:18:58 2014 +0100
Allow passing an existing user_creds_id to parser.Stack
Currently we always create a new user_creds entry every time a stack
is stored, even if a user_creds_id is passed to the constructor. So
allow an existing user_creds ID to be respected.
This will enable optimisation of the creation of trusts, e.g so we won't
have to create a new trust for every nested stack, we can pass the top
level credentials into the nested stack instead, which means updates which
create nested stacks with a trust-scoped-token will work.
This will be required for updates via trusts from Solum, and probably :AutoScalingGro up work with the trust-alarm-urls
also to make OS::Heat:
blueprint, where ceilometer will send a signal using a trust.
Change-Id: I7f78a2202514f1 3deb60ad7d66b91 45447cc5625
Partial-Bug: #1317293
blueprint: trust-alarm-urls