As described in the bug report, filter names used in stack_list API are
not consistent with what users see when creating or retrieving stacks.
We cannot simply change the exposed filter key names because that will
break existing users.
This patch adds a translation logic from STACK_KEYS like 'stack_name' to
its corresponding db column name, i.e. 'name'. The intent is to provide
compatibility with existing use cases while enforcing API consistency
regarding the "properties" a user sees from the API.
At engine API layer, we also try a simple parsing of the 'status' key,
which may be of simple form 'FAILED' or complex form 'CREATE_COMPLETE'.
Reviewed: https:/ /review. openstack. org/188411 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=b910a27d5ff 0b924f3fba3933e 6f90621f3c1bf3
Committed: https:/
Submitter: Jenkins
Branch: master
commit b910a27d5ff0b92 4f3fba3933e6f90 621f3c1bf3
Author: tengqm <email address hidden>
Date: Thu Jun 4 10:09:28 2015 -0400
Fix filter name inconsistency in stack_list
As described in the bug report, filter names used in stack_list API are
not consistent with what users see when creating or retrieving stacks.
We cannot simply change the exposed filter key names because that will
break existing users.
This patch adds a translation logic from STACK_KEYS like 'stack_name' to
its corresponding db column name, i.e. 'name'. The intent is to provide
compatibility with existing use cases while enforcing API consistency
regarding the "properties" a user sees from the API.
At engine API layer, we also try a simple parsing of the 'status' key,
which may be of simple form 'FAILED' or complex form 'CREATE_COMPLETE'.
Change-Id: Ia6fe4345ca9fea f20c3bd020ff454 e5d701a458e
Closes-Bug: 1461838