Fix permissions in example configs #579
Labels
No Label
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 Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#579
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
According to YAML spec octal numbers should start with '0o' (see "changes in version 1.2): https://yaml.org/spec/1.2.2/ext/changes/
Viper supports 1.2 (via go-yaml.v3) but currently violates the spec because of the backwards compatibility:
f6f7691b1f/resolve.go (L233)
f6f7691b1f/resolve.go (L200)
There is not much we could do for validation (viper "just reads" the yaml, all conversions are done afterwards), but we can at least fix the example: either use
0o644
or'0644'
.This could've been such a tasty bug during some future updrade, lucky for us our deployments use
string
currently.Actually, I believe '0o644' is the only future-proof valid option now, unless we cast it to string on our side.