honeybadger 1.3.1 → 1.4.0

data/features/metal.feature

@@ -1,11 +1,13 @@
 Feature: Rescue errors in Rails middleware
 
   Background:
-    Given I have built and installed the "honeybadger" gem
-    And I generate a new Rails application
+    Given I generate a new Rails application
     And I configure the Honeybadger shim
-    And I configure my application to require the "honeybadger" gem
-    And I run the honeybadger generator with "-k myapikey"
+    And I configure Honeybadger with:
+      """
+      config.api_key = 'myapikey'
+      config.logger = Logger.new(STDOUT)
+      """
 
   Scenario: Rescue an exception in the dispatcher
     When I define a Metal endpoint called "Exploder":

data/features/rack.feature

@@ -1,8 +1,5 @@
 Feature: Use the notifier in a plain Rack app
 
-  Background:
-    Given I have built and installed the "honeybadger" gem
-
   Scenario: Rescue and exception in a Rack app
     Given the following Rack app:
       """
@@ -11,6 +8,7 @@ Feature: Use the notifier in a plain Rack app
 
       Honeybadger.configure do |config|
         config.api_key = 'my_api_key'
+        config.logger = Logger.new(STDOUT)
       end
 
       app = Rack::Builder.app do
@@ -29,6 +27,7 @@ Feature: Use the notifier in a plain Rack app
 
       Honeybadger.configure do |config|
         config.api_key = 'my_api_key'
+        config.logger = Logger.new(STDOUT)
         config.ignore_user_agent << /ignore/
       end
 
@@ -52,5 +51,5 @@ Feature: Use the notifier in a plain Rack app
       end
       """
     When I perform a Rack request to "http://example.com:123/test/index?param=value"
-    Then I should not see "** [Honeybadger] Response from Honeybadger:"
+    Then the output should not contain "** [Honeybadger] Response from Honeybadger:"
 

data/features/rails.feature

@@ -1,91 +1,57 @@
 Feature: Install the Gem in a Rails application
 
   Background:
-    Given I have built and installed the "honeybadger" gem
-    And I generate a new Rails application
+    Given I generate a new Rails application
+    And I configure the Honeybadger shim
 
   Scenario: Use the gem without vendoring the gem in a Rails application
-    When I configure the Honeybadger shim
-    And I configure my application to require the "honeybadger" gem
-    And I run the honeybadger generator with "-k myapikey"
-    Then the command should have run successfully
-    And I should receive a Honeybadger notification
+    When I run the honeybadger generator with "-k myapikey"
+    Then I should receive a Honeybadger notification
     And I should see the Rails version
 
-  Scenario: vendor the gem and uninstall
-    When I configure the Honeybadger shim
-    And I configure my application to require the "honeybadger" gem
-    And I unpack the "honeybadger" gem
-    And I run the honeybadger generator with "-k myapikey"
-    Then the command should have run successfully
-    When I uninstall the "honeybadger" gem
-    And I install cached gems
-    And I run "rake honeybadger:test"
-    Then I should see "** [Honeybadger] Response from Honeybadger:"
-    And I should receive two Honeybadger notifications
-
   Scenario: Configure the notifier by hand
-    When I configure the Honeybadger shim
+    When I configure my application to require Honeybadger
     And I configure the notifier to use "myapikey" as an API key
-    And I configure my application to require the "honeybadger" gem
     And I run the honeybadger generator with ""
     Then I should receive a Honeybadger notification
 
   Scenario: Configuration within initializer isn't overridden by Railtie
-    When I configure the Honeybadger shim
-    And I configure usage of Honeybadger
-    Then the command should have run successfully
-    When I configure the notifier to use the following configuration lines:
+    When I configure my application to require Honeybadger
+    And I run the honeybadger generator with "-k myapikey"
+    And I configure Honeybadger with:
       """
       config.api_key = "myapikey"
       config.project_root = "argle/bargle"
       """
-    And I define a response for "TestController#index":
-      """
-      session[:value] = "test"
-      raise RuntimeError, "some message"
-      """
-    And I route "/test/index" to "test#index"
-    And I perform a request to "http://example.com:123/test/index?param=value"
-    Then I should receive a Honeybadger notification
+    And I run `rake honeybadger:test`
+    Then the output should contain "argle/bargle"
 
   Scenario: Try to install without an api key
-    When I configure my application to require the "honeybadger" gem
+    When I configure my application to require Honeybadger
     And I run the honeybadger generator with ""
-    Then I should see "Must pass --api-key or --heroku or create config/initializers/honeybadger.rb"
-
-  Scenario: Configure and deploy using only installed gem
-    When I run "capify ."
-    And I configure the Honeybadger shim
-    And I configure my application to require the "honeybadger" gem
-    And I run the honeybadger generator with "-k myapikey"
-    And I configure my application to require the "capistrano" gem if necessary
-    And I run "cap -T"
-    Then I should see "honeybadger:deploy"
+    Then the output should contain "Must pass --api-key or --heroku or create config/initializers/honeybadger.rb"
 
-  Scenario: Configure and deploy using only vendored gem
-    When I run "capify ."
-    And I configure the Honeybadger shim
-    And I configure my application to require the "honeybadger" gem
-    And I unpack the "honeybadger" gem
+  Scenario: Configure and deploy with Capistrano
+    When I successfully run `capify .`
+    And I configure my application to require Honeybadger
     And I run the honeybadger generator with "-k myapikey"
-    And I uninstall the "honeybadger" gem
-    And I install cached gems
-    And I configure my application to require the "capistrano" gem if necessary
-    And I run "cap -T"
-    Then I should see "honeybadger:deploy"
+    And I run `cap -T`
+    Then the output should contain "honeybadger:deploy"
 
   Scenario: Try to install when the honeybadger plugin still exists
     When I install the "honeybadger" plugin
-    And I configure the Honeybadger shim
     And I configure the notifier to use "myapikey" as an API key
-    And I configure my application to require the "honeybadger" gem
+    And I configure my application to require Honeybadger
     And I run the honeybadger generator with ""
-    Then I should see "You must first remove the honeybadger plugin. Please run: script/plugin remove honeybadger"
+    Then the output should contain "You must first remove the honeybadger plugin. Please run: script/plugin remove honeybadger"
 
   Scenario: Rescue an exception in a controller
-    When I configure the Honeybadger shim
-    And I configure usage of Honeybadger
+    When I configure my application to require Honeybadger
+    And I configure Honeybadger with:
+      """
+      config.api_key = 'myapikey'
+      config.logger = Logger.new(STDOUT)
+      """
     And I define a response for "TestController#index":
       """
       session[:value] = "test"
@@ -95,29 +61,18 @@ Feature: Install the Gem in a Rails application
     And I perform a request to "http://example.com:123/test/index?param=value"
     Then I should receive a Honeybadger notification
 
-  Scenario: The gem should not be considered a framework gem
-    When I configure the Honeybadger shim
-    And I configure my application to require the "honeybadger" gem
-    And I run the honeybadger generator with "-k myapikey"
-    And I run "rake gems"
-    Then I should see that "honeybadger" is not considered a framework gem
-
   Scenario: The app uses Vlad instead of Capistrano
-    When I configure the Honeybadger shim
-    And I configure my application to require the "honeybadger" gem
-    And I run "touch config/deploy.rb"
-    And I run "rm Capfile"
+    When I configure my application to require Honeybadger
+    And I run `touch config/deploy.rb`
+    And I run `rm Capfile`
     And I run the honeybadger generator with "-k myapikey"
-    Then "config/deploy.rb" should not contain "capistrano"
+    Then the file "config/deploy.rb" should not contain "capistrano"
 
   Scenario: Support the Heroku addon in the generator
-    When I configure the Honeybadger shim
-    And I configure the Heroku rake shim
-    And I configure the Heroku gem shim with "myapikey"
-    And I configure my application to require the "honeybadger" gem
+    When I configure the Heroku gem shim with "myapikey"
+    And I configure my application to require Honeybadger
     And I run the honeybadger generator with "--heroku"
-    Then the command should have run successfully
-    And I should receive a Honeybadger notification
+    Then I should receive a Honeybadger notification
     And I should see the Rails version
     And my Honeybadger configuration should contain the following line:
       """
@@ -125,13 +80,10 @@ Feature: Install the Gem in a Rails application
       """
 
   Scenario: Support the --app option for the Heroku addon in the generator
-    When I configure the Honeybadger shim
-    And I configure the Heroku rake shim
-    And I configure the Heroku gem shim with "myapikey" and multiple app support
-    And I configure my application to require the "honeybadger" gem
+    When I configure the Heroku gem shim with "myapikey" and multiple app support
+    And I configure my application to require Honeybadger
     And I run the honeybadger generator with "--heroku -a myapp"
-    Then the command should have run successfully
-    And I should receive a Honeybadger notification
+    Then I should receive a Honeybadger notification
     And I should see the Rails version
     And my Honeybadger configuration should contain the following line:
       """
@@ -139,11 +91,11 @@ Feature: Install the Gem in a Rails application
       """
 
   Scenario: Filtering parameters in a controller
-    When I configure the Honeybadger shim
-    And I configure usage of Honeybadger
-    When I configure the notifier to use the following configuration lines:
+    When I configure my application to require Honeybadger
+    And I configure Honeybadger with:
       """
       config.api_key = "myapikey"
+      config.logger = Logger.new(STDOUT)
       config.params_filters << "credit_card_number"
       """
     And I define a response for "TestController#index":
@@ -154,13 +106,15 @@ Feature: Install the Gem in a Rails application
     And I route "/test/index" to "test#index"
     And I perform a request to "http://example.com:123/test/index?param=value"
     Then I should receive a Honeybadger notification
+    And the request should not contain "blue42"
+    And the request params should contain "FILTERED"
 
   Scenario: Filtering session in a controller
-    When I configure the Honeybadger shim
-    And I configure usage of Honeybadger
-    When I configure the notifier to use the following configuration lines:
+    When I configure my application to require Honeybadger
+    And I configure Honeybadger with:
       """
       config.api_key = "myapikey"
+      config.logger = Logger.new(STDOUT)
       config.params_filters << "secret"
       """
     And I define a response for "TestController#index":
@@ -171,10 +125,16 @@ Feature: Install the Gem in a Rails application
     And I route "/test/index" to "test#index"
     And I perform a request to "http://example.com:123/test/index?param=value"
     Then I should receive a Honeybadger notification
+    And the request should not contain "blue42"
+    And the request session should contain "FILTERED"
 
   Scenario: Filtering session and params based on Rails parameter filters
-    When I configure the Honeybadger shim
-    And I configure usage of Honeybadger
+    When I configure my application to require Honeybadger
+    And I configure Honeybadger with:
+      """
+      config.api_key = 'myapikey'
+      config.logger = Logger.new(STDOUT)
+      """
     And I configure the application to filter parameter "secret"
     And I define a response for "TestController#index":
       """
@@ -185,10 +145,18 @@ Feature: Install the Gem in a Rails application
     And I route "/test/index" to "test#index"
     And I perform a request to "http://example.com:123/test/index?param=value"
     Then I should receive a Honeybadger notification
+    And the request should not contain "red23"
+    And the request should not contain "blue42"
+    And the request session should contain "FILTERED"
+    And the request params should contain "FILTERED"
 
   Scenario: Notify honeybadger within the controller
-    When I configure the Honeybadger shim
-    And I configure usage of Honeybadger
+    When I configure my application to require Honeybadger
+    And I configure Honeybadger with:
+      """
+      config.api_key = 'myapikey'
+      config.logger = Logger.new(STDOUT)
+      """
     And I define a response for "TestController#index":
       """
       session[:value] = "test"
@@ -200,8 +168,12 @@ Feature: Install the Gem in a Rails application
     Then I should receive a Honeybadger notification
 
   Scenario: Notify honeybadger within a metal controller
-    When I configure the Honeybadger shim
-    And I configure usage of Honeybadger
+    When I configure my application to require Honeybadger
+    And I configure Honeybadger with:
+      """
+      config.api_key = 'myapikey'
+      config.logger = Logger.new(STDOUT)
+      """
     And I define a metal response for "TestController#index":
       """
       raise RuntimeError, "some message"
@@ -211,12 +183,47 @@ Feature: Install the Gem in a Rails application
     Then I should receive a Honeybadger notification
 
   Scenario: Reporting 404s
-    When I configure the Honeybadger shim
-    And I configure usage of Honeybadger
-    And I configure the notifier to use the following configuration lines:
+    When I configure my application to require Honeybadger
+    And I configure Honeybadger with:
     """
+    config.api_key = 'myapikey'
+    config.logger = Logger.new(STDOUT)
     config.ignore_only = []
     """
     And I perform a request to "http://example.com:123/this/route/does/not/exist"
-    Then I should see "The page you were looking for doesn't exist."
+    Then the output should contain "The page you were looking for doesn't exist."
+    And I should receive a Honeybadger notification
+
+  Scenario: Asynchronous delivery
+    When I configure my application to require Honeybadger
+    And I configure Honeybadger with:
+      """
+      config.api_key = 'myapikey'
+      config.logger = Logger.new(STDOUT)
+      config.async do |notice|
+        handler = Thread.new do
+          notice.deliver
+        end
+        handler.join
+      end
+      """
+    And I define a response for "TestController#index":
+      """
+      raise RuntimeError, "some message"
+      """
+    And I route "/test/index" to "test#index"
+    And I perform a request to "http://example.com:123/test/index?param=value"
+    Then I should receive a Honeybadger notification
+
+  Scenario: Asynchronous delivery in generator
+    When I configure my application to require Honeybadger
+    And I configure Honeybadger with:
+      """
+      config.api_key = 'myapikey'
+      config.async do |notice|
+        Thread.new { notice.deliver }
+      end
+      """
+    And I run the honeybadger generator with ""
+    Then the output should contain "Temporarily disabling asynchronous delivery"
     And I should receive a Honeybadger notification

data/features/rake.feature

@@ -1,6 +1,4 @@
 Feature: Use the Gem to catch errors in a Rake application
-  Background:
-    Given I have built and installed the "honeybadger" gem
 
   Scenario: Catching exceptions in Rake
     When I run rake with honeybadger

data/features/sinatra.feature

@@ -1,8 +1,5 @@
 Feature: Use the notifier in a Sinatra app
 
-  Background:
-    Given I have built and installed the "honeybadger" gem
-
   Scenario: Rescue an exception in a Sinatra app
     Given the following Rack app:
       """
@@ -11,6 +8,7 @@ Feature: Use the notifier in a Sinatra app
 
       Honeybadger.configure do |config|
         config.api_key = 'my_api_key'
+        config.logger = Logger.new(STDOUT)
       end
 
       class FontaneApp < Sinatra::Base

data/features/step_definitions/metal_steps.rb

@@ -6,7 +6,7 @@ When /^I define a Metal endpoint called "([^\"]*)":$/ do |class_name, definition
     file.puts definition
     file.puts "end"
   end
-  When %{the metal endpoint "#{class_name}" is mounted in the Rails 3 routes.rb} if rails3?
+  step %(the metal endpoint "#{class_name}" is mounted in the Rails 3 routes.rb) if rails3?
 end
 
 When /^the metal endpoint "([^\"]*)" is mounted in the Rails 3 routes.rb$/ do |class_name|
@@ -15,6 +15,7 @@ When /^the metal endpoint "([^\"]*)" is mounted in the Rails 3 routes.rb$/ do |c
   rack_route = "match '/metal(/*other)' => #{class_name}"
   routes = routes[0..-2] + [rack_route, routes[-1]]
   File.open(routesrb, "w") do |f|
+    f.puts "$:<< '#{LOCAL_RAILS_ROOT}'"
     f.puts "require 'app/metal/#{class_name.underscore}'"
     routes.each do |route_line|
       f.puts route_line

data/features/step_definitions/rack_steps.rb

@@ -15,9 +15,9 @@ When /^I perform a Rack request to "([^\"]*)"$/ do |url|
     file.puts %{headers.each { |key, value| puts "\#{key}: \#{value}"}}
     file.puts "body.each { |part| print part }"
   end
-  @terminal.run("ruby #{request_file}")
+  step %(I run `ruby #{request_file}`)
 end
 
 Then /^I should receive a Honeybadger notification for rack$/ do
-  Then %{I should see "You have accessed a deleted account."}
+  step %(The output should contain "You have accessed a deleted account.")
 end

data/features/step_definitions/rails_steps.rb

@@ -0,0 +1,238 @@
+require 'uri'
+require 'active_support/core_ext'
+
+When /^I generate a new Rails application$/ do
+  rails_create_command = !rails3? ? 'rails rails_root' :
+    'rails new rails_root -O -S -G -J -T --skip-gemfile --skip-bundle'
+
+  step %(I successfully run `bundle exec #{rails_create_command}`)
+  step %(I cd to "rails_root")
+
+  require_thread
+
+  monkeypatch_old_version if rails_version == "2.3.14"
+
+  unless rails3?
+    config_gem_dependencies
+    disable_activerecord
+  end
+end
+
+When /^I configure the Honeybadger shim$/ do
+  shim_file = File.join(PROJECT_ROOT, 'features', 'support', 'honeybadger_shim.rb.template')
+  if rails_supports_initializers?
+    target = File.join(rails_root, 'config', 'initializers', 'honeybadger_shim.rb')
+    FileUtils.cp(shim_file, target)
+  else
+    File.open(environment_path, 'a') do |file|
+      file.puts
+      file.write IO.read(shim_file)
+    end
+  end
+end
+
+When /^I configure my application to require Honeybadger$/ do
+  if rails3?
+    # Do nothing - bundler's on it
+  elsif rails_manages_gems?
+    config_gem('honeybadger')
+  else
+    File.open(environment_path, 'a') do |file|
+      file.puts
+      file.puts("require 'honeybadger'")
+      file.puts("require 'honeybadger/rails'")
+    end
+
+    unless rails_finds_generators_in_gems?
+      FileUtils.cp_r(File.join(PROJECT_ROOT, 'generators'), File.join(rails_root, 'lib'))
+    end
+  end
+end
+
+When /^I configure Honeybadger with:$/ do |config|
+  if rails_manages_gems?
+    requires = ''
+  else
+    requires = "require 'honeybadger'"
+  end
+
+  initializer_code = <<-EOF
+    #{requires}
+    Honeybadger.configure do |config|
+      #{config}
+    end
+  EOF
+
+  if rails_supports_initializers?
+    File.open(rails_initializer_file, 'w') { |file| file.write(initializer_code) }
+  else
+    File.open(environment_path, 'a') do |file|
+      file.puts
+      file.puts initializer_code
+    end
+  end
+end
+
+When /^I run the honeybadger generator with "([^\"]*)"$/ do |generator_args|
+  if rails3?
+    step %(I successfully run `./script/rails generate honeybadger #{generator_args}`)
+  else
+    step %(I successfully run `./script/generate honeybadger #{generator_args}`)
+  end
+end
+
+Then /^I should receive (.+) Honeybadger notifications?$/ do |number|
+  number = case number
+           when /^(one|a)$/ then 1
+           when 'two' then 2
+           else number end
+
+  all_output.scan(/\[Honeybadger\] Response from Honeybadger:/).size.should == number
+  step %(the output should contain "123456789")
+end
+
+Then /^the request\s?(url|component|action|params|session|cgi_data|context)? should( not)? contain "([^\"]*)"$/ do |key, negate, expected|
+  notice = all_output.match(/Notice: ({.+})/) ? JSON.parse(Regexp.last_match(1)) : {}
+  hash = key ? notice['request'][key.strip] : notice['request']
+  hash.to_s.send(negate ? :should_not : :should, match(/#{Regexp.escape(expected)}/))
+end
+
+Then /^I should see the Rails version$/ do
+  step %(the output should contain "[Rails: #{rails_version}]")
+end
+
+When /^I define a( metal)? response for "([^\"]*)":$/ do |metal, controller_and_action, definition|
+  controller_class_name, action = controller_and_action.split('#')
+  controller_name = controller_class_name.underscore
+  controller_file_name = File.join(rails_root, 'app', 'controllers', "#{controller_name}.rb")
+  File.open(controller_file_name, "w") do |file|
+    file.puts "class #{controller_class_name} < #{ (metal && rails3?) ? 'ActionController::Metal' : 'ApplicationController'}"
+    file.puts "def consider_all_requests_local; false; end"
+    file.puts "def local_request?; false; end"
+    file.puts "def #{action}"
+    file.puts definition
+    file.puts "end"
+    file.puts "end"
+  end
+end
+
+When /^I perform a request to "([^\"]*)"$/ do |uri|
+  perform_request(uri)
+end
+
+When /^I route "([^\"]*)" to "([^\"]*)"$/ do |path, controller_action_pair|
+  route = if rails3?
+            %(match "#{path}", :to => "#{controller_action_pair}")
+          else
+            controller, action = controller_action_pair.split('#')
+            %(map.connect "#{path}", :controller => "#{controller}", :action => "#{action}")
+          end
+  routes_file = File.join(rails_root, "config", "routes.rb")
+  File.open(routes_file, "r+") do |file|
+    content = file.read
+    content.gsub!(/^end$/, "  #{route}\nend")
+    file.rewind
+    file.write(content)
+  end
+end
+
+When /^I configure the Heroku gem shim with "([^\"]*)"( and multiple app support)?$/ do |api_key, multi_app|
+  heroku_script_bin = File.join(TEMP_DIR, "bin")
+  FileUtils.mkdir_p(heroku_script_bin)
+  heroku_script     = File.join(heroku_script_bin, "heroku")
+  heroku_env_vars = <<-VARS
+HONEYBADGER_API_KEY    => myapikey
+APP_NAME            => cold-moon-2929
+BUNDLE_WITHOUT      => development:test
+COMMIT_HASH         => lj32j42ss9332jfa2
+DATABASE_URL        => postgres://fchovwjcyb:QLPVWmBBbf4hCG_YMrtV@ec3-107-28-193-23.compute-1.amazonaws.com/fhcvojwwcyb
+LANG                => en_US.UTF-8
+LAST_GIT_BY         => kensa
+RACK_ENV            => production
+SHARED_DATABASE_URL => postgres://fchovwjcyb:QLPVwMbbbF8Hcg_yMrtV@ec2-94-29-181-224.compute-1.amazonaws.com/fhcvojcwwyb
+STACK               => bamboo-mri-1.9.2
+URL                 => cold-moon-2929.heroku.com
+  VARS
+  single_app_script = <<-SINGLE
+#!/bin/bash
+if [ $1 == 'config' ]
+then
+  echo "#{heroku_env_vars}"
+fi
+  SINGLE
+
+  multi_app_script = <<-MULTI
+#!/bin/bash
+if [[ $1 == 'config' && $2 == '--app' ]]
+then
+  echo "#{heroku_env_vars}"
+fi
+  MULTI
+
+  File.open(heroku_script, "w") do |f|
+    if multi_app
+      f.puts multi_app_script
+    else
+      f.puts single_app_script
+    end
+  end
+  FileUtils.chmod(0755, heroku_script)
+
+  ENV['PATH'] = "#{heroku_script_bin}#{File::PATH_SEPARATOR}#{ENV['PATH']}"
+end
+
+Then /^my Honeybadger configuration should contain the following line:$/ do |line|
+  configuration_file = if rails_supports_initializers?
+    rails_initializer_file
+  else
+    rails_non_initializer_honeybadger_config_file
+  end
+
+  configuration = File.read(configuration_file)
+  if ! configuration.include?(line.strip)
+    raise "Expected text:\n#{configuration}\nTo include:\n#{line}\nBut it didn't."
+  end
+end
+
+When /^I configure the application to filter parameter "([^\"]*)"$/ do |parameter|
+  if rails3?
+    application_filename = File.join(rails_root, 'config', 'application.rb')
+    application_lines = File.open(application_filename).readlines
+
+    application_definition_line       = application_lines.detect { |line| line =~ /Application/ }
+    application_definition_line_index = application_lines.index(application_definition_line)
+
+    application_lines.insert(application_definition_line_index + 1,
+                             "    config.filter_parameters += [#{parameter.inspect}]")
+
+   File.open(application_filename, "w") do |file|
+     file.puts application_lines.join("\n")
+   end
+  else
+   controller_filename = application_controller_filename
+   controller_lines = File.open(controller_filename).readlines
+
+   controller_definition_line       = controller_lines.detect { |line| line =~ /ApplicationController/ }
+   controller_definition_line_index = controller_lines.index(controller_definition_line)
+
+   controller_lines.insert(controller_definition_line_index + 1,
+                           "    filter_parameter_logging #{parameter.inspect}")
+
+   File.open(controller_filename, "w") do |file|
+     file.puts controller_lines.join("\n")
+   end
+  end
+end
+
+When /^I install the "([^\"]*)" plugin$/ do |plugin_name|
+  FileUtils.mkdir_p("#{rails_root}/vendor/plugins/#{plugin_name}")
+end
+
+When /^I configure the notifier to use "([^\"]*)" as an API key$/ do |api_key|
+  steps %{
+    When I configure Honeybadger with:
+      """
+      config.api_key = #{api_key.inspect}
+      """
+  }
+end