Skip to content

Improve how we handle deprecation warnings

Jeremy Jackson requested to merge jejacks0n/tooling/improve-gitlab-experiment-deprecation-handling into master

What does this MR do and why?

Part of #350944

This improves the overall deprecation behavior in a few ways.

  1. It disables deprecation warnings for production like environments -- which might happen across the board based on corrective actions taken from gitlab-com/gl-infra/production#6278 (comment 832455637). In either case, we're going to be extra careful and not log any deprecation warnings on non dev/test environments for now.
  2. We have examples of the notable deprecation warnings for several of the items that are in #350944

As we resolve the deprecation warnings, we can comment in the relevant item to the disallowed list, and any use of them will result in an exception and not simply a warning. This will help us ensure we stay resolved on these moving forward, and the logic in gitlab-experiment can be removed around these deprecation warnings.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports