We can completely remove 'RESOLVE' translations involving client
lookups in resource init. As we are doing translation before create
and update, it seems we can avoid it.
However, we would need other translations, like 'REPLACE' for property
vaidations(ex. required properties that would be replaced by deprecated
properties). This would be done only when strict_validate=True to avoid
this with template-validate.
Reviewed: https:/ /review. openstack. org/290301 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=0bf9463bfce b25d7b98a8fdd84 b61521b8c013cb
Committed: https:/
Submitter: Jenkins
Branch: master
commit 0bf9463bfceb25d 7b98a8fdd84b615 21b8c013cb
Author: Rabi Mishra <email address hidden>
Date: Wed Mar 9 11:33:49 2016 +0530
Don't RESOLVE translate in resource init
We can completely remove 'RESOLVE' translations involving client
lookups in resource init. As we are doing translation before create
and update, it seems we can avoid it.
However, we would need other translations, like 'REPLACE' for property validate= True to avoid
vaidations(ex. required properties that would be replaced by deprecated
properties). This would be done only when strict_
this with template-validate.
Change-Id: Ie80bdd10726a8f c8a8787b78db93a cffd333137f
Closes-Bug: #1554927
Partial-Bug: #1554380