Grace period for SSH key restrictions
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
A customer wants to restrict certain types of SSH keys but are not able to see who is currently using what type of key or avoid people from being locked out. There is no grace period or something.
Context: The customer is running a self-managed instance. Users are actively using GitLab for SCM and CI/CD. Being locked out of GitLab because of an unsupported SSH key could lead to disruption of work and they want to avoid that.
Current solution for this problem Their only feasible option of informing users is placing an announcement banner. Although this will reach the majority, it doesn't mean people are actually doing it. There is no way to identify these people that are using an unsupported SSH key.
Proposal: Add a feature so that SSH key restrictions are not enforced immediately but start with a grace period where people are informed when using an unsupported key. Similar to a deprecation notice. This allows users some time to change their key before the change is enforced and people can't use the old key types anymore.