-
Notifications
You must be signed in to change notification settings - Fork 63
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
[v0.5] s4: Fixes 227 #404
[v0.5] s4: Fixes 227 #404
Conversation
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.
The PR fails because the drone config uses rancher/rancher:v2.9-head
and that image quietly changed its base image from registry.suse.com/bci-base
to bci-micro
, and the latter doesn't include zypper
.
I fixed this on other PRs that still use drone by moving it back to v2.9.0-alpha1
@ericpromislow Thanks for the insights! It seems like the required change is not related to this port in any way and should be applied is a separate PR. Then this one can be rebased. |
The requested change has nothing to do with this port PR
Depends and needs to be rebased on #406 |
a089b27
to
d6e54d0
Compare
When a Setting is created, the following checks take place: | ||
|
||
- If set, `disable-inactive-user-after` must be zero or a positive duration (e.g. `240h`). | ||
- If set, `delete-inactive-user-after` must be zero or a positive duration (e.g. `240h`). |
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.
The MinDeleteInactiveUserAfter
check does not seem to be documented. Is that intentional ?
Issue:
Port of #390
Problem
Solution
CheckList