aarifullin/frostfs-api
1
0
Fork 0
forked from TrueCloudLab/frostfs-api
Code Pull requests Activity

[#37] Add body message to balance requests

Browse source 
Signed-off-by: Alex Vanin <alexey@nspcc.ru>
This commit is contained in:
Alex Vanin 2020-08-11 11:12:37 +03:00 committed by Stanislav Bogatyrev
parent 327c476ecf
commit d22c2557cb
1 changed files with 35 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

33
accounting/service.proto
View file

@ -6,6 +6,8 @@ option go_package = "github.com/nspcc-dev/neofs-api-go/accounting";
option csharp_namespace = "NeoFS.API.Accounting";
import "refs/types.proto";
import "service/meta.proto";
import "service/verify.proto";
// The service provides methods for obtaining information
// about the account balance in NeoFS system.
@ -22,8 +24,23 @@ service Accounting {
// To gain access to the requested information, the request body must be formed
// according to the requirements from the system specification.
message BalanceRequest {
// Carries user identifier in NeoFS system for which the balance is requested.
message Body {
// Carries user identifier in NeoFS system for which the balance
// is requested.
refs.OwnerID owner_id = 1;
}
// Body of the balance request message.
Body body = 1;
// Carries request meta information. Header data is used only to regulate
// message transport and does not affect request execution.
service.RequestMetaHeader meta_header = 2;
// Carries request verification information. This header is used to
// authenticate the nodes of the message route and check the correctness
// of transmission.
service.RequestVerificationHeader verify_header = 3;
}
// Decimal represents the decimal numbers.
@ -39,6 +56,20 @@ message Decimal {
//
// The amount of funds is calculated in decimal numbers.
message BalanceResponse {
message Body {
// Carries the amount of funds on the account.
Decimal balance = 1;
}
// Body of the balance response message.
Body body = 1;
// Carries response meta information. Header data is used only to regulate
// message transport and does not affect request execution.
service.ResponseMetaHeader meta_header = 2;
// Carries response verification information. This header is used to
// authenticate the nodes of the message route and check the correctness
// of transmission.
service.ResponseVerificationHeader verify_header = 3;
}