Make listing chains with generated wallet #1638
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 milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1638
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "aarifullin/frostfs-node:fix/apemngr_list_chain"
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?
apemanager
's methodListChains
no longer validates request senderfrostfs-cli ape-manager list
can be run with-g
optionClose #1389
On a second thought, it is not so simple.
Private access rules may be a feature.
Like not anyone can list containers in the namespace.
what do you think @alexvanin @realloc ?
@fyrchik wrote in #1638 (comment):
I suppose such way for listing doesn't violate anything. Listing chains ignore signature checks. So, every target can be listed by raw listing with
That is different, blockchain API is private, storage API is public.
This PR won't be merged because it breaks privacy giving the free access to list container APE rules and an owner isn't able to restrict this action (if we consider a public network).
As I've said above, the rules can be listed with
neo-go contract testinvokefunction
:#1638 (comment)
ape-manager
service should allow list APE chains with node wallet #1389Pull request closed