Introduce a method to list targets in Policy contract #78

New issue

Closed

opened 2024-02-06 13:18:47 +00:00 by aarifullin · 2 comments

aarifullin commented

2024-02-06 13:18:47 +00:00

Member

The chain listing has become more unambiguous - check here. So, we cannot list all chains by ListByPrefix('n', "", "") - the invocation lists only root-namespace chains.

But one problem is still relevant: we cannot determine which targets are kept in contract - we may never clean them out if their names are "forgotten". One method ListTargets should be enough to fix everything

Also, this could be consistent with ControlAPI that manages local overrides, because we already have such method

The chain listing has become more unambiguous - check [here](https://git.frostfs.info/TrueCloudLab/frostfs-contract/issues/67). So, we cannot list _all_ chains by `ListByPrefix('n', "", "")` - the invocation lists only root-namespace chains. But one problem is still relevant: we cannot determine which targets are kept in contract - we may never clean them out if their names are "forgotten". One method `ListTargets` should be enough to fix everything Also, this could be consistent with ControlAPI that manages local overrides, because we already have such method

👍 1

aarifullin added the

discussion

label 2024-02-06 13:18:47 +00:00

alexvanin commented

2024-02-06 13:43:13 +00:00

Owner

By the way, is ListTargets going to return both namespace and container targets? Can we distinguish them on a contract level or they are all the same?

There is a workaround to list all available namespace chains: ask FrostFS ID contract about all available namespaces and make additional requests per namespace in policy contract. I appreciate any simplifications in this routine. By the way, is `ListTargets` going to return both namespace and container targets? Can we distinguish them on a contract level or they are all the same?

aarifullin self-assigned this 2024-02-06 13:43:27 +00:00

aarifullin commented

2024-02-06 15:12:31 +00:00

Author

Member

There is a workaround to list all available namespace chains: ask FrostFS ID contract about all available namespaces and make additional requests per namespace in policy contract. I appreciate any simplifications in this routine.

By the way, is ListTargets going to return both namespace and container targets? Can we distinguish them on a contract level or they are all the same?

Yes, we will do distinguish them

> There is a workaround to list all available namespace chains: ask FrostFS ID contract about all available namespaces and make additional requests per namespace in policy contract. I appreciate any simplifications in this routine. > > By the way, is `ListTargets` going to return both namespace and container targets? Can we distinguish them on a contract level or they are all the same? Yes, we will do distinguish them

👍 1

aarifullin referenced this issue from a pull request that will close it,

2024-02-09 14:45:22 +00:00

policy: Introduce ListTargets method for Policy contract #79

aarifullin referenced this issue from a pull request that will close it,

2024-02-19 12:08:38 +00:00

[#78] policy: Introduce ListTargets method for Policy contract #80