Allow optional sending/receiving request headers from reporting api to storage layer
In the case of role based authorization control it can be useful to have the http request information in the storage layer. For example, if fine-grained tenant grouping information is stored in the database, being able to retrieve metadata based on the user's role(s) would be necessary.
Propose that methods like MeterController
if 'request_headers' in kwargs:
return [Sample.
else:
return [Sample.
Since this is optional for every storage class, it would require no changes to any storage implementation classes. It would enable the flexibility to write storage drivers which use the request header information, or to extend existing drivers to do so.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Eric Pendergrass
- Direction:
- Needs approval
- Assignee:
- Eric Pendergrass
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- gordon chung
Related branches
Related bugs
Sprints
Whiteboard
is this covered by RBAC policies? if so i'm going to close this. -- gordc (18.6.15)