Geo: database.yml template does not check whether primary or secondary

Overview

The database.yml template always append the geo: database section if Geo is enabled. This should only happen on a secondary site.

Impacted categories

The following categories relate to this issue:

• gdk-reliability - e.g. When a GDK action fails to complete.
• gdk-usability - e.g. Improvements or suggestions around how the GDK functions.
• gdk-performance - e.g. When a GDK action is slow or times out.

Steps to replicate (optional)

1. Follow the instructions from the Advanced Installation.
2. Try to access the primary site
3. Get the error below

Geo::TrackingBase::SecondaryNotConfigured at /admin

Geo secondary database is not configured

Proposal (optional)

Include an extra check in the database.yml to verify whether we are on the primary or secondary

Environment (optional)

• Operating system name: <!-- output of `uname -a` command -->
• Architecture: <!-- output of `arch` command -->
• The contents of your gdk.yml (if any)
• Ruby version: <!-- output of `ruby --version` command -->
• GDK version: <!-- output of `git rev-parse --short HEAD` command -->