Implicit yaml tag resolver being registered for YaqlYamlLoader (which is
user to load MuranoPL classes as YAML documents with embedded YAQL
statements) was being registered in the default YAML Dumper which is
used for any YAML serialization.
This was leading to inability to load more then one HOT-based package
per API service lifetime: the first package which was uploaded was
causing the leakage of YAQL statements into the global tag resolver.
This global resolver was used for all subsequent load attempts, so plain
yaml documents with Heat templates were attempted to be loaded as
MuranoPL classes.
This patch fixes this behavior by registering the implicit resolver
without helper method (which actually registers the resolvers at default
Dumper).
Reviewed: https:/ /review. openstack. org/179176 /git.openstack. org/cgit/ openstack/ murano/ commit/ ?id=779fd3cd230 4c9276b65407372 ccda6fa9a6b639
Committed: https:/
Submitter: Jenkins
Branch: master
commit 779fd3cd2304c92 76b65407372ccda 6fa9a6b639
Author: Alexander Tivelkov <email address hidden>
Date: Thu Apr 30 20:27:40 2015 +0300
Fixed YAQL tag leakage to YAML loader
Implicit yaml tag resolver being registered for YaqlYamlLoader (which is
user to load MuranoPL classes as YAML documents with embedded YAQL
statements) was being registered in the default YAML Dumper which is
used for any YAML serialization.
This was leading to inability to load more then one HOT-based package
per API service lifetime: the first package which was uploaded was
causing the leakage of YAQL statements into the global tag resolver.
This global resolver was used for all subsequent load attempts, so plain
yaml documents with Heat templates were attempted to be loaded as
MuranoPL classes.
This patch fixes this behavior by registering the implicit resolver
without helper method (which actually registers the resolvers at default
Dumper).
Change-Id: Icd3b6d354bcb10 5c2c25f842ede07 7d539e9c246
Closes-Bug: #1450547