Define a tailored Scoper for each CDM
As of now, we have a single CDM Scoper that is meant to work for all CDM plugins. However, we know that in real life, it's not possible to end up with the same structure for all of them since they can represent disjoint types of resources.
The object of this blueprint would be to:
- Change the audit_scope_handler property implemented in BaseStrategy
- Remove audit_scope_handler from the current BaseStrategy and move it within the CDM collector base as abstract
- Implement a default scope handler that does nothing and that can be used from within the CDM collector base
- Rename the DefaultScope as ComputeScope and override the audit_scope_handler property in the Compute Collector
- Make sure the API exposes a unified Audit Scope format
-> Define a pluggable list of sections within the unified JSON schema
- ....
At the end each CDM collector would have its own CDMScoper but they should all be exposed as one big standardized JSON schema format so that if a strategy actually uses 2 or more CDMs, then the audit scope given can filter each CDM.
Blueprint information
- Status:
- Complete
- Approver:
- Alexander Chadin
- Priority:
- Medium
- Drafter:
- Vincent Françoise
- Direction:
- Approved
- Assignee:
- Hidekazu Nakamura
- Definition:
- Approved
- Series goal:
- Accepted for queens
- Implementation:
- Implemented
- Milestone target:
- queens-1
- Started by
- aditi sharma
- Completed by
- aditi sharma
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
[WIP] CDM Scoping
Addressed by: https:/
Add cdm-scoping spec
Addressed by: https:/
[WIP] Add cdm-scoping
Addressed by: https:/
Update doc and add release note about cdm-scoping
Addressed by: https:/
Update getting scoped storage CDM
Work Items
Dependency tree
* Blueprints in grey have been implemented.