summaryrefslogtreecommitdiff
path: root/releasenotes/notes
diff options
context:
space:
mode:
authorPeter Stachowski <peter@tesora.com>2016-08-09 17:39:37 -0400
committerPeter Stachowski <peter@tesora.com>2016-08-15 20:11:48 +0000
commit21f56bc75ce8212e97c9044b6b223bde30eda252 (patch)
tree03d5636a34285429ead7e4622fb89b6d47dc7dcc /releasenotes/notes
parent980b5d2cc4fe60a4ac259439c58668defa64e893 (diff)
downloadtrove-21f56bc75ce8212e97c9044b6b223bde30eda252.tar.gz
Module re-apply does not reflect updated values
If you apply a module, remove it, update the module with a new name, and apply it again, module-query will still show the old name. This also applies to datastore, datastore_version and type. All four attributes are now updated correctly and scenario tests added. When writing the scenario tests it became evident that resetting a module from a datastore to all_datastores was broken too, so this was fixed (along with all_datastore_versions). This fix required a change to the Trove client as well. Change-Id: Ic2e9226bcd31c4a79d84ecb7941a47875eabd73d Depends-On: I0f226f09db08f635c542b27d8d2f898050d327fa Closes-Bug: #1611525 Closes-Bug: #1612430
Diffstat (limited to 'releasenotes/notes')
-rw-r--r--releasenotes/notes/module_reapply_update_values-1fb88dc58701368d.yaml9
1 files changed, 9 insertions, 0 deletions
diff --git a/releasenotes/notes/module_reapply_update_values-1fb88dc58701368d.yaml b/releasenotes/notes/module_reapply_update_values-1fb88dc58701368d.yaml
new file mode 100644
index 00000000..1616bd5b
--- /dev/null
+++ b/releasenotes/notes/module_reapply_update_values-1fb88dc58701368d.yaml
@@ -0,0 +1,9 @@
+---
+fixes:
+ - Applying a module again will now relect the
+ update name, type, datastore and datastore_version
+ values.
+ Bug 1611525
+ - Updating a module with all_datastores and
+ all_datastore_versions now works correctly.
+ Bug 1612430