Audit API supports new force option

Depends-on:Ia08694d2fb76907ea14e64116af2e722fe930063 Change-Id: Ib2d221ea9c994dea396c54cc8d2d32237025a1d4 Implements: blueprint add-force-field-to-audit
2019-05-09 14:48:25 +08:00
parent 3b9364d4c7
commit 2afd0dfcf5
7 changed files with 67 additions and 3 deletions
--- a/releasenotes/notes/add-force-field-to-audit-4bcaeedfe27233ad.yaml
+++ b/releasenotes/notes/add-force-field-to-audit-4bcaeedfe27233ad.yaml
@@ -0,0 +1,7 @@
+---
+features:
+  - |
+    Add force field to Audit. User can set --force to enable the new option when
+    launching audit. If force is True, audit will be executed despite of ongoing
+    actionplan. The new audit may create a wrong actionplan if they use the same
+    data model.