Add validating util for target names #26

New Issue

Closed

opened 2023-12-06 11:32:16 +00:00 by aarifullin · 2 comments

aarifullin commented

2023-12-06 11:32:16 +00:00

Collaborator

It would be very useful if a target name was checked for pattern matching.

Let's consider a target name native:object//LxGyWyLAezAkMi/* (means ResourceFormatRootContainerObjects) - it would be correct to check if the name is valid before adding it to local override storage

It would be very useful if a target name was checked for [pattern](https://git.frostfs.info/TrueCloudLab/policy-engine/src/branch/master/schema/native/consts.go#L12-L28) matching. Let's consider a target name `native:object//LxGyWyLAezAkMi/*` (means `ResourceFormatRootContainerObjects`) - it would be correct to check if the name is valid before adding it to local override storage

aarifullin added the

enhancement

discussion

labels 2023-12-06 11:32:16 +00:00

dkirillov commented

2023-12-06 13:52:45 +00:00

Collaborator

Should we also add the similar check for s3 resources?

aarifullin commented

2023-12-07 10:58:43 +00:00

Poster

Collaborator

Should we also add the similar check for s3 resources?

I think - yes, we should but this can be perfomed optionally. We rather need to check the pattern matching before adding local overrides to local db in ffs-node

> Should we also add the similar check for s3 resources? I think - yes, we should but this can be perfomed optionally. We rather need to check the pattern matching before adding local overrides to local db in ffs-node

aarifullin referenced this issue

2023-12-07 15:52:49 +00:00

schema: Add resource name validation method #27