-
Notifications
You must be signed in to change notification settings - Fork 549
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement '--expiry' flag for 'mc admin user svcacct add & edit' #4570
Conversation
@kaankabalak while verifying edit without
Server side I can see error as below
|
Hi @shtripat, I can't seem to reproduce this for now, are you using the latest MinIO Server code while running these commands? |
Yes, latest master build of
|
Thanks @shtripat, I will investigate further and get back to you 👍 |
My apologies @shtripat, looks like I have pasted the edit command incorrectly on the PR instructions. The following should work for a service account with access key
|
Ah yes, this works as expected. I should have looked at help of the command :( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Verified the changes.
@kaankabalak please resolve the conflicts. |
ca75c63
to
ffe2a1b
Compare
Done @shtripat 👍 |
Description
This commit implements the
--expiry
flag for themc admin user svcacct add
andmc admin user svcacct edit
commands, allowing users to set expiration dates for service accounts throughmc
.The expiry date can be set in the following formats:
2023-06-24
2023-06-24T10:00
2023-06-24T10:00:00
2023-06-24T10:00:00Z
2023-06-24T10:00:00-07:00
Motivation and Context
We would like to implement this functionality as the APIs to set/edit expiration for service accounts already have been implemented in minio/madmin-go#170.
How to test this PR?
mc
binary from this branchfoobar1
,foobar2
,foobar3
,foobar4
andfoobar5
using themc admin user add
command.--expiry
flag is present:--expiry
flagJ123C4ZXEQN8RK6ND35I
, make sure that it can be successfully edited as follows:--expiry
flagTypes of changes
Checklist:
commit-id
orPR #
here)