ores.iam.role_grant_request_role
Table of Contents
The roles an iam.role_grant approval request asks for, one row each. A row is
identified by the request and the role. When the request is approved, IAM
grants each role the account does not already hold, and records that it
applied it.
1. Flags
2. Left
The role grant request the role belongs to.
References ores_iam_role_grant_requests_tbl.request_id (soft FK).
ctx.generate_uuid()
3. Right
The role asked for.
References ores_iam_roles_tbl.id (soft FK).
ctx.generate_uuid()
4. Columns
4.1. applied_at
When IAM applied the role after the request was approved, or null until it has. Applying is done once: a role the account already held is marked applied without a grant, and a role taken away after it was applied is not granted again, because the request is still approved but no longer unapplied.
std::nullopt
5. SQL
5.1. Flags
6. Foreign keys
6.1. request_id
The role grant request the role belongs to; must exist in ores_iam_role_grant_requests_tbl.
6.2. role_id
The role asked for; must exist in ores_iam_roles_tbl.
7. Repository
8. C++
8.1. Flags
8.2. Domain includes
#include <optional> #include <string> #include <boost/uuid/uuid.hpp>
8.3. Entity includes
#include <string>
8.4. Conventions
8.5. Table display
| column | header |
|---|---|
| request_id | Request |
| role_id | Role |
| applied_at | Applied |
| version | Version |
8.6. Presentation
A row is identified by the pair it links, so the model declares no key field.
9. See also
- ores.iam.role_grant_request – the request a role belongs to.
- ores.iam.role – the role asked for.