BigW Consortium Gitlab
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.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
ci | Loading commit data... | |
clusters | Loading commit data... | |
base_policy_spec.rb | Loading commit data... | |
deploy_key_policy_spec.rb | Loading commit data... | |
environment_policy_spec.rb | Loading commit data... | |
global_policy_spec.rb | Loading commit data... | |
group_policy_spec.rb | Loading commit data... | |
issuable_policy_spec.rb | Loading commit data... | |
issue_policy_spec.rb | Loading commit data... | |
namespace_policy_spec.rb | Loading commit data... | |
note_policy_spec.rb | Loading commit data... | |
personal_snippet_policy_spec.rb | Loading commit data... | |
project_policy_spec.rb | Loading commit data... | |
project_snippet_policy_spec.rb | Loading commit data... | |
protected_branch_policy_spec.rb | Loading commit data... | |
user_policy_spec.rb | Loading commit data... |