roo_on_rails 1.21.0 → 2.1.2

data/.circleci/config.yml.erb

@@ -1,15 +1,36 @@
 # To update the build configuration, edit the "builds" array below and run:
 # erb .circleci/config.yml.erb > .circleci/config.yml
+
+
+# The default Ruby containers modify the behaviour of Bundler in a way that breaks
+# the CI since it makes it harder to run multiple apps in a single container
+# See https://github.com/docker-library/docs/pull/1221/files for a summary
+# Unsettting these variables restores the default behaviour:-
+#   * BUNDLE_APP_CONFIG
+#   * GEM_HOME
+#   * BUNDLE_PATH
+#   * BUNDLE_BIN
+common_ruby_environment: &common_ruby_environment
+  environment:
+    RAILS_ENV: test
+    PGHOST: 127.0.0.1
+    PGUSER: postgres
+    POSTGRES_HOST_AUTH_METHOD: "trust"
+common_pg_environment_vars: &common_pg_environment_vars
+    POSTGRES_USER: postgres
+    POSTGRES_DB: ror_testapp_test
+    POSTGRES_HOST_AUTH_METHOD: "trust"
 <%
   builds = [
-		['2.3.4', 'rails_3'],
-		['2.3.4', 'rails_4'],
-		['2.4.1', 'rails_4'],
-		['2.3.4', 'rails_5'],
-		['2.4.1', 'rails_5'],
-		['2.3.4', 'rails_5_1'],
-		['2.4.1', 'rails_5_1'],
-		['2.4.1', 'rails_5_2']
+    ['2.4.6', 'rails_4'],
+    ['2.4.6', 'rails_5'],
+    ['2.4.6', 'rails_5_1'],
+    ['2.4.6', 'rails_5_2'],
+    ['2.5.5', 'rails_4'],
+    ['2.5.5', 'rails_5'],
+    ['2.5.5', 'rails_5_1'],
+    ['2.5.5', 'rails_5_2'],
+    ['2.6.5', 'rails_6']
   ]
 %>
 version: 2
@@ -17,11 +38,13 @@ jobs:
 <% builds.each do |ruby,variant| %>
   build_<%= ruby %>_<%= variant %>:
     docker:
-      - image: deliveroo/multiruby
+      - image: ruby:<%= ruby %>-alpine
+        <<: *common_ruby_environment
       - image: postgres:9.6-alpine
         environment:
           PGDATA: /dev/shm/pgdata
-      - image: redis:3-alpine
+          <<: *common_pg_environment_vars
+      - image: redis:4-alpine
     steps:
       - checkout
 
@@ -33,28 +56,50 @@ jobs:
             ln -s /dev/shm/tmp ~/project/tmp
 
       - run:
-          name: Select build variant (Ruby <%= ruby %>, <%= variant %>)
+          name: Setup requirements
+          command: |
+            apk add --update git bash build-base postgresql-dev sqlite-dev tzdata nodejs
+
+      - run:
+          name: Configure bundler
           command: |
-            rbenv local <%= ruby %> ;
-            gem install bundler ;
+            unset \
+              BUNDLE_APP_CONFIG \
+              GEM_HOME \
+              BUNDLE_PATH \
+              BUNDLE_BIN
             bundle config --local gemfile $PWD/gemfiles/<%= variant %>.gemfile
 
       - restore_cache:
-          keys: 
+          keys:
             - v2-bundle-<%= ruby %>-<%= variant %>-{{ .Branch }}
             - v2-bundle-<%= ruby %>-<%= variant %>
             - v2-bundle-<%= ruby %>
 
-      - run: 
-          name: Install dependencies
+      - run:
+          name: Install bundle
           command: |
+            unset \
+              BUNDLE_APP_CONFIG \
+              GEM_HOME \
+              BUNDLE_PATH \
+              BUNDLE_BIN
             bundle install --jobs=3 --retry=3 --path=$PWD/vendor/bundle
 
+      # The default Ruby containers modify the behaviour of Bundler in a way that breaks
+      # the CI since it makes it harder to run multiple apps in a single container
+      # See https://github.com/docker-library/docs/pull/1221/files for a summary
+      # Unsettting the variables restores the default behaviour
       - run:
           name: Run test suite
           command: |
-            unset RACK_ENV &&
-            unset RAILS_ENV &&
+            unset \
+              RACK_ENV \
+              RAILS_ENV \
+              BUNDLE_APP_CONFIG \
+              GEM_HOME \
+              BUNDLE_PATH \
+              BUNDLE_BIN
             bundle exec rspec
 
       - save_cache:

data/.codecov.yml

@@ -2,6 +2,9 @@ codecov:
   notify:
     require_ci_to_pass: yes
 
+ignore:
+  - "spec/support"
+
 coverage:
   precision: 2
   round: down

data/Appraisals

@@ -1,31 +1,37 @@
-appraise 'rails-3' do
-  gem 'rails', '~> 3.2'
-  gem 'sqlite3'
-  gem 'sidekiq', '< 5'
-  gem 'pg', '~> 0.11'
-end
-
 appraise 'rails-4' do
   gem 'rails', '~> 4.2'
-  gem 'sqlite3'
+  gem 'sqlite3', '~> 1.3.6'
   gem 'pg', '~> 0.11'
+  gem 'sprockets', '~>3.0'
+  gem 'rake', '13.0.1'
 end
 
 appraise 'rails-5' do
   gem 'rails', '~> 5.0.0'
-  gem 'sqlite3'
+  gem 'sqlite3', '~> 1.3.6'
   gem 'pg', '~> 0.18'
+  gem 'rake', '13.0.1'
 end
 
 appraise 'rails-5-1' do
   gem 'rails', '~> 5.1.0'
-  gem 'sqlite3'
+  gem 'sqlite3', '~> 1.3.6'
   gem 'pg', '~> 0.18'
+  gem 'rake', '13.0.1'
 end
 
 appraise 'rails-5-2' do
   gem 'rails', '~> 5.2.0'
   gem 'bootsnap', '>= 1.1.0', require: false
-  gem 'sqlite3'
+  gem 'sqlite3', '~> 1.3.6'
+  gem 'pg', '~> 0.18'
+  gem 'rake', '13.0.1'
+end
+
+appraise 'rails-6' do
+  gem 'rails', '~> 6.0.3'
+  gem 'bootsnap', '>= 1.1.0', require: false
+  gem 'sqlite3', '~> 1.4'
   gem 'pg', '~> 0.18'
+  gem 'rake', '13.0.1'
 end

data/CHANGELOG.md

@@ -1,3 +1,41 @@
+# v2.1.2
+
+Bug fix:
+
+- fixes PopulateEnvFromJWT caching issue where a key that couldn't be fetched would be cached
+
+# v2.1.0
+
+Features:
+
+- Rails 6 compatibility
+
+# v2.0.0-pre.2
+
+Features:
+
+- Removes routemaster
+
+# v2.0.0-pre.1
+
+Features:
+
+- Remove New Relic
+
+# v1.23.0 (2019-04-24)
+
+Features:
+
+- Setting DATABASE_STATEMENT_TIMEOUT to -1 will prevent the app setting any timeout.
+  Setting timeouts from the app conflicts with PGBouncer and should be disabled if
+  using one.
+
+# v1.22.0 (2018-08-29)
+
+Features:
+
+ - Allows specifying `BASE_NEW_RELIC_APP_NAME` instead of `NEW_RELIC_APP_NAME`, which reports to New Relic per Hopper service.
+
 # v1.21.0 (2018-03-27)
 
 Features:

data/README.md

@@ -17,17 +17,17 @@
 
 - [Installation](#installation)
 - [Library usage](#library-usage)
-  - [New Relic configuration](#new-relic-configuration)
   - [Rack middleware](#rack-middleware)
+    - [Disabling SSL enforcement](#disabling-ssl-enforcement)
   - [Database configuration](#database-configuration)
   - [Sidekiq](#sidekiq)
-  - [HireFire](#hirefire)
   - [Logging](#logging)
   - [Identity](#identity)
   - [Google OAuth authentication](#google-oauth-authentication)
   - [Datadog Integration](#datadog-integration)
-  - [Routemaster Client](#routemaster-client)
-  - [API Authentication ](#api-authentication)
+    - [Heroku metrics](#heroku-metrics)
+    - [Custom application metrics](#custom-application-metrics)
+  - [API Authentication](#api-authentication)
 - [Command features](#command-features)
   - [Usage](#usage)
   - [Description](#description)
@@ -48,11 +48,6 @@ Remove the following gems from your Gemfile, as they're provided and configured
 by `roo_on_rails`:
 
 - `dotenv`
-- `newrelic_rpm`
-
-Remove the following configuration files:
-
-- `newrelic.yml` or `config/newrelic.yml`
 
 Also remove any other gem-specific configuration from your repository.
 
@@ -62,23 +57,19 @@ And then execute:
 
 Then re-run your test suite to make sure everything is shipshape.
 
-## Library usage
+## Running specs
 
-### New Relic configuration
+To run the specs locally, you will need to run the following command:
 
-We enforce configuration of New Relic.
+```ruby
+bundle config --local gemfile $PWD/gemfiles/<%= variant %>.gemfile
+```
+
+Where `<%= variant %>` is the Rails version you'd like to test (e.g. `rails_5_2`).
 
-1. Your app must be loaded with a `NEW_RELIC_LICENSE_KEY` environment variable,
-   otherwise it will abort.
-2. No `new_relic.yml` file may be presentin your app. Overrides to New Relic settings
-   through [environment
-   variables](https://docs.newrelic.com/docs/agents/ruby-agent/installation-configuration/ruby-agent-configuration)
-   is permitted.
-3. The `NEW_RELIC_APP_NAME` environment variable must be defined
-   such that the app will be properly registered in New Relic.
+`bundle exec rspec` should then work as normal.
 
-No further configuration is required for production apps as the gem configures
-our standard settings.
+## Library usage
 
 ### Rack middleware
 
@@ -104,6 +95,11 @@ To do this, you can set the `ROO_ON_RAILS_DISABLE_SSL_ENFORCEMENT` to `YES`.
 The database statement timeout will be set to a low value by default. Use
 `DATABASE_STATEMENT_TIMEOUT` (milliseconds, default 200) to customise.
 
+When using a PGBouncer, setting the timeout from the application will cause
+inconsistent results. The timeout should always be set using the RDS parameter
+group in thise case. To prevent the app trying to set a timeout, set
+`DATABASE_STATEMENT_TIMEOUT` to -1.
+
 For database creation and migration (specifically the `db:create`, `db:migrate`,
 `db:migrate:down` and `db:rollback` tasks) a much higher statement timeout is
 set by default. Use `MIGRATION_STATEMENT_TIMEOUT` (milliseconds, default 10000)
@@ -138,48 +134,6 @@ NB. If you are migrating to SLA-based queue names, do not set `SIDEKIQ_ENABLED`
 to `true` before your old queues have finished processing (this will prevent
 Sidekiq from seeing the old queues at all).
 
-### HireFire
-
-#### For Web Dynos
-
-Web dynos can be autoscaled by HireFire _only_ if it has been configured to use the `Web.Logplex.Load` source and the Heroku runtime metrics lab feature has been enabled:
-
-```bash
-$ heroku labs:enable log-runtime-metrics -a your-service-name-here
-```
-
-You will also need a log drain for HireFire, but the RooOnRails helper below should configure this for you. You can check with
-
-```bash
-$ heroku drains | grep hirefire
-https://logdrain.hirefire.io (d.00000000-0000-0000-0000-000000000000)
-
-# No drain? Add with:
-$ heroku drains:add -a your-service-name-here https://logdrain.hirefire.io
-```
-
-([HireFire docs for set up](https://help.hirefire.io/guides/logplex/load-logplex))
-
-#### For Sidekiq Workers
-
-When `HIREFIRE_TOKEN` is set an endpoint will be mounted at `/hirefire` that
-reports the required worker count as a function of queue latency. By default we
-add queue names in the style 'within1day', so if we notice an average latency in
-that queue of more than an set threshold we'll request one more worker. If we
-notice less than a threshold we'll request one less worker. These settings can
-be customised via the following ENV variables
-
-- `WORKER_INCREASE_THRESHOLD` (default 0.5)
-- `WORKER_DECREASE_THRESHOLD` (default 0.1)
-
-When setting the manager up in the HireFire web ui, the following settings must
-be used:
-
-- name: 'worker'
-- type: 'Worker.HireFire.JobQueue'
-- ratio: 1
-- decrementable: 'true'
-
 ### Logging
 
 For clearer and machine-parseable log output, the Rails logger is replaced by an
@@ -302,16 +256,6 @@ The following tags will automatically be added to all your metrics and their val
   * `HOPPER_APP_NAME`+`HOPPER_ECS_CLUSTER_NAME` – automatically set by Hopper (e.g. `notifications-staging`);
   * Defaults to `unknown`.
 
-### Routemaster Client
-
-When `ROUTEMASTER_ENABLED` is set to `true` we attempt to configure [`routemaster-client`](https://github.com/deliveroo/routemaster-client) on your application. In order for this to happen, set the following environment variables:
-
-* `ROUTEMASTER_URL` – the full URL of your Routemaster application (mandatory)
-* `ROUTEMASTER_UUID` – the UUID of your application, e.g. `logistics-dashboard` (mandatory)
-* `ROUTEMASTER_VERIFY_SSL` – set to false if your Routemaster application is not served with a valid cert. (optional)
-
-If you then want to enable the publishing of events onto the event bus, you need to set `ROUTEMASTER_PUBLISHING_ENABLED` to `true` and implement publishers as needed. An example of how to do this is detailed in [`README.routemaster_client.md`](README.routemaster_client.md).
-
 ### API Authentication
 
 RooOnRails provides a concern which will make adding rotatable API authentication to your service a breeze:
@@ -393,6 +337,11 @@ The command is designed to fix issues in many cases.
 Pull requests are welcome on GitHub at
 `https://github.com/deliveroo/roo_on_rails`.
 
+## Releasing
+
+1. Bump the version number in `lib/roo_on_rails/version.rb
+1. Add an entry to the changelog
+1. After merging to master release e.g. `bundle exec rake release`
 
 ## License
 

data/appraise

@@ -5,7 +5,7 @@
 require 'yaml'
 
 
-RUBIES = YAML.load_file('.travis.yml')['rvm']
+RUBIES = ['2.4.5', '2.5.5', '2.6.5']
 APPRAISALS = `appraisal list`.strip.split(/\s+/)
 
 # setup

data/exe/roo_on_rails

@@ -36,6 +36,11 @@ module RooOnRails
       end
 
       def run
+        # Force output to be unbuffered, otherwise the CI
+        # tests will fail because the parent app won't see
+        # the log output from the test app
+        $stdout.sync = true
+        $stderr.sync = true
         _assert_argv_length(0..0)
         require 'roo_on_rails/sidekiq/loader'
         RooOnRails::Sidekiq::Loader.run

data/gemfiles/rails_4.gemfile

@@ -7,7 +7,9 @@ gem "guard-rspec"
 gem "appraisal"
 gem "webmock"
 gem "pg", "~> 0.11"
-gem "sqlite3"
+gem "sqlite3", "~> 1.3.6"
 gem "rails", "~> 4.2"
+gem "sprockets", "~>3.0"
+gem "rake", "13.0.1"
 
 gemspec path: "../"

data/gemfiles/rails_5.gemfile

@@ -7,7 +7,8 @@ gem "guard-rspec"
 gem "appraisal"
 gem "webmock"
 gem "pg", "~> 0.18"
-gem "sqlite3"
+gem "sqlite3", "~> 1.3.6"
 gem "rails", "~> 5.0.0"
+gem "rake", "13.0.1"
 
 gemspec path: "../"

data/gemfiles/rails_5_1.gemfile

@@ -7,7 +7,8 @@ gem "guard-rspec"
 gem "appraisal"
 gem "webmock"
 gem "pg", "~> 0.18"
-gem "sqlite3"
+gem "sqlite3", "~> 1.3.6"
 gem "rails", "~> 5.1.0"
+gem "rake", "13.0.1"
 
 gemspec path: "../"

data/gemfiles/rails_5_2.gemfile

@@ -7,8 +7,9 @@ gem "guard-rspec"
 gem "appraisal"
 gem "webmock"
 gem "pg", "~> 0.18"
-gem "sqlite3"
+gem "sqlite3", "~> 1.3.6"
 gem "rails", "~> 5.2.0"
 gem "bootsnap", ">= 1.1.0", require: false
+gem "rake", "13.0.1"
 
 gemspec path: "../"

data/gemfiles/{rails_3.gemfile → rails_6.gemfile}

@@ -6,9 +6,10 @@ gem "guard"
 gem "guard-rspec"
 gem "appraisal"
 gem "webmock"
-gem "pg", "~> 0.11"
-gem "sqlite3"
-gem "rails", "~> 3.2"
-gem "sidekiq", "< 5"
+gem "pg", "~> 0.18"
+gem "sqlite3", "~> 1.4"
+gem "rails", "~> 6.0.3"
+gem "bootsnap", ">= 1.1.0", require: false
+gem "rake", "13.0.1"
 
 gemspec path: "../"