gRPC 6 ALREADY_EXISTS vs 7 PERMISSION_DENIED
Both gRPC 6 (ALREADY_EXISTS) and 7 (PERMISSION_DENIED) belong to the gRPC Status Codes category. 6 indicates that the entity that a client attempted to create already exists. For example, a file or directory that the RPC was supposed to create already exists. Meanwhile, 7 means that the caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
描述
The entity that a client attempted to create already exists. For example, a file or directory that the RPC was supposed to create already exists.
何时出现
A create operation failed because a resource with the same unique identifier or name already exists in the system.
如何修复
Use a different identifier, or switch to an upsert/update operation if overwriting is acceptable. Check for existing resources before creating.
描述
The caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
何时出现
The authenticated user lacks the required role, scope, or policy to perform this action. Different from UNAUTHENTICATED (code 16), which means no credentials at all.
如何修复
Verify the caller has the correct IAM role, API scope, or access policy. Check RBAC configuration on the server side.
主要区别
gRPC 6: The entity that a client attempted to create already exists. For example, a file or directory that the RPC was supposed to create already exists.
gRPC 7: The caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
You encounter 6 when a create operation failed because a resource with the same unique identifier or name already exists in the system.
You encounter 7 when the authenticated user lacks the required role, scope, or policy to perform this action. Different from UNAUTHENTICATED (code 16), which means no credentials at all.
何时使用哪个
For 6 (ALREADY_EXISTS): Use a different identifier, or switch to an upsert/update operation if overwriting is acceptable. Check for existing resources before creating. For 7 (PERMISSION_DENIED): Verify the caller has the correct IAM role, API scope, or access policy. Check RBAC configuration on the server side.