feature/frostfs_system_attribute #10
No reviewers
Labels
No labels
P0
P1
P2
P3
good first issue
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
6 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-api-go#10
Loading…
Reference in a new issue
No description provided.
Delete branch "dkirillov/frostfs-api-go:feature/frostfs_system_attribute"
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?
ff94485312
to3369fd4240
WIP: feature/frostfs_system_attributeto feature/frostfs_system_attribute@ -18,2 +18,4 @@
)
// SysAttributePrefixFrostFS is a prefix of key to system attribute.
const SysAttributePrefixFrostFS = "__FROSTFS__"
I am wondering if it is better to use
*NeoFS
for legacy stuff and no suffix for a new one.What do you think?
I suggest keep using a prefix to avoid naming collisions and keep logical separations fro attributes affecting system behavior.
Ah! I get it now. Agree =)
@fyrchik, dont we need any system prefix? it may not have any relations to a product name but be more neutral, e.g.
__SYSTEM__
I like the
__SYSTEM__
idea, but we probably need another round of PRs for that :)@ -11,6 +11,9 @@ import (
// prefix of keys to subnet attributes.
const attrSubnetPrefix = "__NEOFS__SUBNET_"
What you think about having
// Deprecated: use FrostFS 'attrSubnetPrefixFrostFS'
to such code or is it too early for this?@fyrchik @dkirillov @carpawell
I would just remove that but there are also other thoughts on it.
3369fd4240
to31be126b74
31be126b74
tocd2e46a17c