[#81] rpc: Fix apemanager rpc service name
All checks were successful
DCO action / DCO (pull_request) Successful in 1m4s
Tests and linters / Tests (1.19) (pull_request) Successful in 1m10s
Tests and linters / Tests (1.20) (pull_request) Successful in 1m27s
Tests and linters / Lint (pull_request) Successful in 1m44s
Tests and linters / Tests with -race (pull_request) Successful in 1m48s

* Introduce `frostfsServiceNamePrefix` for rpc interface
  since `apemanager` uses `frostfs` root instead `neo.fs`.

Signed-off-by: Airat Arifullin <a.arifullin@yadro.com>
This commit is contained in:
Airat Arifullin 2024-05-06 14:28:49 +03:00
parent 0fe6b9adbb
commit b171364079
2 changed files with 9 additions and 2 deletions

View file

@ -6,7 +6,7 @@ import (
"git.frostfs.info/TrueCloudLab/frostfs-api-go/v2/rpc/common"
)
const serviceAPEManager = serviceNamePrefix + "apemanager.APEManagerService"
const serviceAPEManager = frostfsServiceNamePrefix + "apemanager.APEManagerService"
const (
rpcAPEManagerAddChain = "AddChain"

View file

@ -1,3 +1,10 @@
package rpc
const serviceNamePrefix = "neo.fs.v2."
const (
// serviceNamePrefix is still used in "old" services but should be
// considered as deprecated. Since new services use "frostfs" root,
// `frostfsServiceNamePrefix` must be used for their rpc interface.
serviceNamePrefix = "neo.fs.v2."
frostfsServiceNamePrefix = "frostfs.v2."
)