Move SignMessage
away from control/server
package #1092
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1092
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This makes it necessary to import server package in client code just to sign the message.
func SignMessage(key *ecdsa.PrivateKey, msg SignedMessage) error {
cc @alexvanin
It could be in the
control
package itself, which is imported incontrol/server
anyway.Moving
SignMessage
to the control package would cause a cyclic import of packages. It might then be necessary to create a separate package.@alexvanin Can you describe the issue in more detail?
Sure. In my project I import two dependencies.
SignMessage
to sign Control API requests to update policy chainsThose dependencies also use these packages:
And those packages contain
init
function to initializae gRPC structure which leads to runtime error in the applicationMy fix was to copy
sign.go
file to my repo and avoid package import.SignMessage
to separate package #1132