e7b1d201dd
read_project can be prevented by a very expensive condition, which we want to avoid, while still not writing manual SQL queries. read_project_for_iids is used by read_issue_iid and read_merge_request_iid to satisfy both of those constraints, and allow the declarative policy runner to use its normal caching strategy.
20 lines
717 B
Ruby
20 lines
717 B
Ruby
class IssuePolicy < IssuablePolicy
|
|
# This class duplicates the same check of Issue#readable_by? for performance reasons
|
|
# Make sure to sync this class checks with issue.rb to avoid security problems.
|
|
# Check commit 002ad215818450d2cbbc5fa065850a953dc7ada8 for more information.
|
|
|
|
desc "User can read confidential issues"
|
|
condition(:can_read_confidential) do
|
|
@user && IssueCollection.new([@subject]).visible_to(@user).any?
|
|
end
|
|
|
|
desc "Issue is confidential"
|
|
condition(:confidential, scope: :subject) { @subject.confidential? }
|
|
|
|
rule { confidential & ~can_read_confidential }.policy do
|
|
prevent :read_issue
|
|
prevent :read_issue_iid
|
|
prevent :update_issue
|
|
prevent :admin_issue
|
|
end
|
|
end
|