-
Notifications
You must be signed in to change notification settings - Fork 25
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
Sandbox 554 #404
Merged
Merged
Sandbox 554 #404
Changes from 5 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
d481e7f
Made IdentityClaims required
sbryzak 56a4804
minor
sbryzak d9243c5
Merge remote-tracking branch 'origin/master' into SANDBOX-554
sbryzak d838764
added DeactivationTimestamp to UserSignup.Status
sbryzak 8685dc7
slight improvement to docs
sbryzak 3b0919b
modified type
sbryzak 2bf1b71
Merge remote-tracking branch 'origin/master' into SANDBOX-554
sbryzak 6478d42
fixed
sbryzak File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
shouldn't it be stored in one of the
status.conditions
, instead? We already add a status condition when a user is activated or banned, so why using something different for deactivations?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.
ah never mind, this is the expected time of deactivation, not the actual one (ie, after the user was deactivated).
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.
so this field will need to be updated when a user is moved to another tier.
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.
Let's maybe rename it to
ExpectedTimeOfDeactivation
or something like that to make it clear.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.
Also, could you please explain why you decided to use
string
? what is the expected format/content?Why don't you use
metav1.Time
as we use in conditions?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.
I agree with @MatousJobanek. Something like
ExpectedTimeOfDeactivation
withmetav1.Time
type would look better.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.
I've renamed it to
ScheduledDeactivationTimestamp
, and also modified the type to usemetav1.Time
instead of a string to bring it inline with the rest of the API (before I saw these comments, so at least we were all on the same page ;).