Pre-receive Secret Detection - Project-level visibility
Problem to solve
How should we determine when to show the pre-receive setting for a given project? Currently, it shows under some scenarios where the customer does not have access to enable the feature, and they get an unhelpful error message. This problem has been discussed in an MR and during a Secret Detection team call.
There are currently two independent feature flags that can impact the feature's availability:
pre_receive_secret_detection_beta_release
pre_receive_secret_detection_push_check
In addition to the feature flags, feature availability can also be influenced by a project's license (the feature is only available to Ultimate users?) and an instance-level setting to enable/disable pre-receive secret detection (associated with the FF pre_receive_secret_detection_beta_release
?)
Proposal
- Document feature flags and their behavior so that users can understand why the feature may not be available for a given project or instance.
- Update the UI to display the feature in different ways, depending on specific criteria. Thus far there are 5 scenarios to account for (see designs for scenario specifics)
Edited by Michael Fangman