<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=341959) </details> <!--IssueSummary end--> The following discussion from !70012 should be addressed: - [ ] @dstull started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/70012#note_684382418): (+4 comments) > I'm not sure about this and other uses of `fail_import` that I've added ... > > What is the usual rule here on setting this to `true` or `false`? #### Technical Note: The labkit-ruby upgrade (part of upgrading to Ruby 3.0) injects info into logs - to track which deployment stage we execute on (main, cny)- _after_ the event leaves gitlab-rails. Since it writes the `stage` log field, it overwrites any `stage:` value, so don't use this value in the logs. See !111590