d13669716a
In GitLab EE, a GitLab instance can be read-only (e.g. when it's a Geo secondary node). But in GitLab CE it also might be useful to have the "read-only" idea around. So port it back to GitLab CE. Also having the principle of read-only in GitLab CE would hopefully lead to less errors introduced, doing write operations when there aren't allowed for read-only calls. Closes gitlab-org/gitlab-ce#37534.
35 lines
779 B
Ruby
35 lines
779 B
Ruby
module Keys
|
|
class LastUsedService
|
|
TIMEOUT = 1.day.to_i
|
|
|
|
attr_reader :key
|
|
|
|
# key - The Key for which to update the last used timestamp.
|
|
def initialize(key)
|
|
@key = key
|
|
end
|
|
|
|
def execute
|
|
# We _only_ want to update last_used_at and not also updated_at (which
|
|
# would be updated when using #touch).
|
|
key.update_column(:last_used_at, Time.zone.now) if update?
|
|
end
|
|
|
|
def update?
|
|
return false if ::Gitlab::Database.read_only?
|
|
|
|
last_used = key.last_used_at
|
|
|
|
return false if last_used && (Time.zone.now - last_used) <= TIMEOUT
|
|
|
|
!!redis_lease.try_obtain
|
|
end
|
|
|
|
private
|
|
|
|
def redis_lease
|
|
Gitlab::ExclusiveLease
|
|
.new("key_update_last_used_at:#{key.id}", timeout: TIMEOUT)
|
|
end
|
|
end
|
|
end
|