Permissions Policies and Supported Actions
This chapter describes fine-grained permissions management for your FunctionGraph. If your account does not need individual IAM users, then you may skip over this chapter.
By default, new IAM users do not have any permissions assigned. You need to add a user to one or more groups, and assign permissions policies to these groups. The user then inherits permissions from the groups it is a member of. This process is called authorization. After authorization, the user can perform specified operations on FunctionGraph based on the permissions.
You can grant users permissions by using roles and policies. Roles are a type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. Policies define API-based permissions for operations on specific resources under certain conditions, allowing for more fine-grained, secure access control of cloud resources.
Policy-based authorization is recommended if you want to allow or deny the access to an API.
An account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user queries functions using an API, the user must have been granted permissions that allow the FunctionGraph:function:list action.
Supported Actions
There are two kinds of policies: system-defined policies and custom policies. If the permissions preset in the system do not meet your requirements, you can create custom policies and apply these policies to user groups for refined access control. Operations supported by policies are specific to APIs. The following are common concepts related to policies:
- Permissions: Defined by actions in a custom policy.
- APIs: REST APIs that can be called by a user who has been granted specific permissions.
- Actions: Specific operations that are allowed or denied.
- IAM projects and enterprise projects: Type of projects for which an action will take effect. Policies that contain actions for both IAM and enterprise projects can be used and take effect for both IAM and Enterprise Management. Policies that only contain actions for IAM projects can be used and only take effect for IAM. For details about the differences between IAM and enterprise projects, see What Are the Differences Between IAM and Enterprise Management?
The check mark (√) and cross symbol (x) respectively indicate that an action takes effect or does not take effect for the corresponding type of projects.
Table 1 lists the API actions supported by FunctionGraph.
| Permission | API | Action | IAM Project | Enterprise Project |
|---|---|---|---|---|
| Querying a function list | GET /v2/{project_id}/fgs/functions | FunctionGraph:function:list | √ | √ |
| Querying the metadata of a function | GET /v2/{project_id}/fgs/functions/{function_urn}/config | FunctionGraph:function:getConfig | √ | √ |
| Querying the code of a function | GET /v2/{project_id}/fgs/functions/{function_urn}/code | FunctionGraph:function:getCode | √ | √ |
| Creating a function | POST /v2/{project_id}/fgs/functions | FunctionGraph:function:create | √ | √ |
| Deleting a function or function version | DELETE /v2/{project_id}/fgs/functions/{function_urn} | FunctionGraph:function:delete | √ | √ |
| Modifying the code of a function | PUT /v2/{project_id}/fgs/functions/{function_urn}/code | FunctionGraph:function:updateCode | √ | √ |
| Modifying the metadata of a function | PUT /v2/{project_id}/fgs/functions/{function_urn}/config | FunctionGraph:function:updateConfig | √ | √ |
| Publishing a function version | POST /v2/{project_id}/fgs/functions/{function_urn}/versions | FunctionGraph:function:createVersion | √ | √ |
| Querying the versions of a function | GET /v2/{project_id}/fgs/functions/{function_urn}/versions | FunctionGraph:function:listVersion | √ | √ |
| Creating an alias for a function version | POST /v2/{project_id}/fgs/functions/{function_urn}/aliases | FunctionGraph:function:createAlias | √ | √ |
| Modifying the alias information about a function version | PUT /v2/{project_id}/fgs/functions/{function_urn}/aliases/{alias_name} | FunctionGraph:function:updateAlias | √ | √ |
| Deleting an alias of a function version | DELETE /v2/{project_id}/fgs/functions/{function_urn}/aliases/{alias_name} | FunctionGraph:function:deleteAlias | √ | √ |
| Querying the alias information about a function version | GET /v2/{project_id}/fgs/functions/{function_urn}/aliases/{alias_name} | FunctionGraph:function:getAlias | √ | √ |
| Querying all version aliases of a function | GET /v2/{project_id}/fgs/functions/{function_urn}/aliases | FunctionGraph:function:listAlias | √ | √ |
| Querying all triggers of a function | GET /v2/{project_id}/fgs/triggers/{function_urn} | FunctionGraph:trigger: listSpecifiedFunctionTriggers | √ | √ |
| Querying the information about a trigger | GET /v2/{project_id}/fgs/triggers/{function_urn}/{trigger_type_code}/{trigger_id} | FunctionGraph:trigger:get | √ | √ |
| Deleting all triggers of a function | DELETE /v2/{project_id}/fgs/triggers/{function_urn} | FunctionGraph:trigger: deleteSpecifiedFunctionTriggers | √ | √ |
| Creating a trigger | POST /v2/{project_id}/fgs/triggers/{function_urn} | FunctionGraph:trigger:create | √ | √ |
| Deleting a trigger | DELETE /v2/{project_id}/fgs/triggers/{function_urn}/{trigger_type_code}/{trigger_id} | FunctionGraph:trigger:delete | √ | √ |
| Implementing synchronous function invocation | POST /v2/{project_id}/fgs/functions/{function_urn}/invocations | FunctionGraph:function:invoke | √ | √ |
| Implementing asynchronous function invocation | POST /v2/{project_id}/fgs/functions/{function_urn}/invocations-async | FunctionGraph:function:invokeAsync | √ | √ |
