frostfs-cli bearer create
UX #512
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 project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#512
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Now we have the following obligatory flags for
frostfs-cli bearer create
:As a common user, I would prefer to avoid looking for the current epoch.
I suggest
-i
and-n
to equal the current epoch and make these flags optional;-x
obligatory but require a relative number instead of absolute (-x 10
means that I want the token to be valid for the next 10 epochs)All epoch flags support
+N
syntax for relative epochs, for example+0
means the current epoch,+10
-- 10 epochs from the current one.Is it enough for you needs?
We can set
+0
as a default for some flags, though.@fyrchik Shall we say it somehow in
--help
, it's not clear for me from the existing description? Eg.+N for relative epochs supported
And I still think that a common user shouldn't be required to set
--issued-at
and--not-valid-before
. Why not make them optional?@EliChin This is already in the documentation. Or is it written unclear?
@dstepanov-yadro Sorry, didn't notice this since looking for this information in the flags description themselves. If so, we can keep the help section as it is and hope that our users will be more observant than me.