Add force field to Audit

Registered by licanwei on 2019-04-08

As now, Watcher doesn't allow to launch a new audit when there is actionplan ongoing.
This is because if the new audit has the same data model as the ongoing actionplan, the new audit may create a wrong actionplan.
But if there are different data model scope, we should allow the new audit to run.
We want to give the choice to User, if User set force to True when launching audit, Watcher will execute the audit even other actionplan is ongoing.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
licanwei
Direction:
Approved
Assignee:
licanwei
Definition:
Approved
Series goal:
Accepted for train
Implementation:
Implemented
Milestone target:
milestone icon train-1
Started by
licanwei on 2019-04-28
Completed by
Dantali0n on 2019-09-05

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#/q/topic:bp/add-force-field-to-audit

Addressed by: https://review.openstack.org/653931
    Add a force field to audit

Gerrit topic: https://review.opendev.org/#/q/topic:bp/add-force-field-to-audit

Addressed by: https://review.opendev.org/653931
    Add a force field to audit

Addressed by: https://review.opendev.org/657211
    Add force field to Audit

Addressed by: https://review.opendev.org/657944
    Audit API supports new force option

Addressed by: https://review.opendev.org/658244
    Add force field to api-ref

Addressed by: https://review.opendev.org/658966
    update api version history

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.