resource group
- 17 Jul 2024
- Print
- PDF
resource group
- Updated on 17 Jul 2024
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
summary
TROCCO's Team feature allows each team to be assigned a role for a resource group.
Members belonging to a team to which a role is granted can perform operations authorized by the role.
role permission
The scope of operating privileges controlled by roles for resource groups can be broadly divided into the following two categories
* Resource Group
* Each resource (belonging to a resource group)
The operations allowed for each role are as follows
Authority to operate on resource groups
| Role | Resource Group Administrator | Resource Group Editor | Resource Group Operator | Resource Group Viewer | No Role | Supplemental | Supplemental
| --- | --- | --- | --- | --- | --- | --- |
| リソースグループの編集 | ✓ | - | - | - | - | リソースグループ名およびメモの編集が可能 |
| リソースグループの削除 | ✓ | - | - | - | - | |
| リソースグループの権限設定 | ✓ | - | - | - | - | チームに対するロール付与または削除が可能 |
| Viewing a list of resources in a resource group | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | - | | |
| View Resource Group Details | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓
Operating privileges for each resource
| Role | Resource Group Administrator | Resource Group Editor | Resource Group Operator | Resource Group Viewer | No Role | Supplemental | Supplemental
| --- | --- | --- | --- | --- | --- | --- |
| Edit Resource | ✓ | ✓ | ✓ | - - - - - - Add Resource to Resource Group Includes Operations |
| Duplicate resources | ✓ | ✓ | ✓ | - | - | - | Connection information, dbt Git repository, and dbt job settings cannot be duplicated |
| リソースの削除 | ✓ | ✓ | - | - | - | |
| リソースの実行 | ✓ | ✓ | ✓ | - | - | |
| View Resource | ✓ | ✓ | ✓(*) | ✓(*) | ✓(*) | - | * For Operator and Viewer roles
dbt Git repository, connection information detail screen is not available |
| View job execution logs | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | - | | |
Author's exception privileges
The creator of a resource group or resource has the same operating privileges as a user with the Resource Group Administrator role for each.
Duplicate Roles
In cases where a resource group has different roles for multiple teams, users who belong to multiple teams with different roles will have duplicate roles for the resource group in question.
In this case, a role with broader privileges is applied to the user in question.
The inclusion relationship between roles is "resource group administrator ⊃ resource group editor ⊃ resource group operator ⊃ resource group viewer".
The following is a concrete example to illustrate.
* There are users who belong to both the "engineering team" and the "sales team".
* The "Data Analysis Resource Group" is a group of
* The engineering team is assigned the role of resource group editor.
* The sales team is assigned the role of resource group operator.
At this time, users can perform the operations allowed by the Resource Group Editor role on the Data Analysis Resource Group and the resources under it.
Resource Group List Screen
The Resource Group List screen allows you to view a list of resource groups that exist in your TROCCO account and to create, edit, and delete resource groups.
Resource group displayed on the Resource Group List screen
All resource groups created in a TROCCO account will appear in the Resource Group List screen, including resource groups that have not been granted roles in the team to which they belong.
Create new resource group
Authority to create resource groups
Account administrator or higher privileges are required.
For details on how to change permissions, see User Permission Settings.
Resource Group Details Screen
Click each resource group name or detail on the Resource Group List screen to display.
The following is the Resource Group Details screen as seen by a user with the Resource Group Administrator role.
Editing
Edit resource group name and notes.
Deleted
Delete a resource group.
Once a resource group is deleted, it cannot be restored. Please note
(iii) Authority setting
Grant roles for resource groups to each team.
4) Deletion of roles
Delete roles granted to the team.
(5) Resource group creator
The resource group creator is displayed.
The resource group creator has the same operating privileges as a user with the resource group administrator role for the resource group in question.
⑥ Resource list
A list of resources is displayed.
By clicking on the tabs, you can switch the type of resource to be displayed.
User without role
If a user does not have a role for the resource group in question, the resource list will not be displayed.
(7) Resource details
Click to go to the detail screen of the corresponding resource.
Detailed screen for each resource
The following is an example of a detailed screen of transfer settings as seen from the perspective of a user with the Resource Group Administrator role.
User without role
If a user does not have a role for the resource group that contains the resource in question, he/she will not be able to view the resource details screen.
(1) Execution
Run resources.
Only users with the role of operator or higher can operate the system.
2) Editing
Edit resource.
Only users with the role of Resource Group Editor or higher may operate.
Adding a resource to a resource group
* Adding resources to a resource group is done from the Create New or Edit screen of each resource.
* One resource cannot be added to multiple resource groups.
(iii) Duplication
Duplicate resources.
Only users with the role of Resource Group Editor or higher may operate.
Deleted
Delete resources.
Only users with the role of Resource Group Editor or higher may operate.
Once a resource is deleted, it cannot be restored. Please note
5) Resource creator
The resource creator is displayed.
The resource creator has the same operating privileges as a user with the Resource Group Administrator role for the resource in question.
6) Reflected in Git
Git repository integration
Git repositories can be linked to resource groups.
For more information, please refer to About Git Repository Linkage.
Was this article helpful?