Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable defer_rails_initialization config by environment variable only #1790

Conversation

kaylareopelle
Copy link
Contributor

Overview

Configs are loaded during initialization. This fix was placed behind a feature flag referencing the config value, but that value will always be false at initialization, so the bug fix was unreachable.

Environment variables are accessible before initialization. The environment variable NEW_RELIC_DEFER_RAILS_INITIALIZATION may be set to true to enable this option.

TODO:

  • Fix unit tests

Resolves: #662

kaylareopelle and others added 6 commits December 15, 2022 12:49
Configs are loaded during initialization. This fix was placed behind a
feature flag referencing the config value, but that value will always
be falsey at initialization, so the bugfix was unreachable.

This change will always use the new, split initialization process.
…tialization' of github.com:newrelic/newrelic-ruby-agent into bugfix/rails-frameworks-forced-to-load-during-agent-initialization
@kaylareopelle kaylareopelle force-pushed the bugfix/rails-frameworks-forced-to-load-during-agent-initialization branch from 8b75702 to 1ea36e4 Compare February 3, 2023 20:28
@kaylareopelle
Copy link
Contributor Author

Opened on this branch by mistake

@kaylareopelle kaylareopelle deleted the bugfix/rails-frameworks-forced-to-load-during-agent-initialization branch February 22, 2023 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RPM forces Rails frameworks to load during initialization
1 participant