ores.iam.role_grant_request
Table of Contents
The IAM detail of an iam.role_grant approval request. The request itself, who
asked, when, why and where it stands, is the inbox's record; this row names
the account that would hold the roles, keyed by the request it details. The
roles asked for are rows of ores.iam.role_grant_request_role, one each, so a
request may ask for many.
The account is usually the person who asked, but a system may ask on a
person's behalf, so it is a column of its own rather than the request's
requested_by.
Who asked for which role is not every member's business, so the generated
reads require iam::role_grant_requests:read, as every generated read
requires its resource's read code. The person who asked reads their own requests
through the inbox's inbox.v1.ops.list_my_approval_requests. See
Authorised reads.
1. Flags
2. Columns
2.1. request_id
The approval request this row details. FK reference to ores_inbox_approval_requests_tbl.
2.2. account_id
The account that would hold the roles. FK reference to ores_iam_accounts_tbl.
3. Foreign keys
3.1. request_id
3.2. account_id
4. SQL
4.1. Flags
5. C++
5.1. Flags
5.2. Repository
5.3. Domain includes
#include <string> #include <boost/uuid/uuid.hpp>
5.4. Conventions
5.5. Table display
| column | header |
|---|---|
| request_id | Request |
| account_id | Account |
| modified_by | Modified By |
| version | Version |
5.6. Custom repository methods
6. See also
- Approval requests – the record this row details.
- ores.iam.account – the account that would hold the roles.
- ores.iam.role_grant_request_role – the roles asked for.