There's no reason to force the user to specify the name of a Zaqar queue.
In fact, doing so makes it difficult for users to create multiple instance
of the same template without having all of the messages go into a single
queue (and without deleting the shared queue when one of the stacks is
deleted).
We now autogenerate a sensible randomised name if none is provided.
Reviewed: https:/ /review. openstack. org/404834 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=01487ebbbbc eb07e9ffc604fe6 4a08d7ed27d995
Committed: https:/
Submitter: Jenkins
Branch: master
commit 01487ebbbbceb07 e9ffc604fe64a08 d7ed27d995
Author: Zane Bitter <email address hidden>
Date: Tue Nov 22 11:42:23 2016 -0500
Make the name of a Zaqar queue optional
There's no reason to force the user to specify the name of a Zaqar queue.
In fact, doing so makes it difficult for users to create multiple instance
of the same template without having all of the messages go into a single
queue (and without deleting the shared queue when one of the stacks is
deleted).
We now autogenerate a sensible randomised name if none is provided.
Change-Id: I5195d8c0dd413a 8f1bd28c2a8ef7a 3191c74f882
Partial-Bug: #1637304