Looker 4.8 introduces a change to where Looker stores Git SSH deploy keys:
Before Looker 4.8 — Git SSH deploy keys were stored in the server’s native SSH directory,
Looker 4.8 and up — Git SSH deploy keys are stored in a Looker-controlled directory,
Note: Only Git SSH deploy keys for new LookML projects will be placed in this new directory—keys for existing projects will remain in
You will need to make some changes if you are running Looker as a cluster without a shared storage directory (network file system). Specifically, you will need to start syncing this new directory across all nodes in the cluster. See below for more details.
You do not need to do anything if
- Your instance is hosted by Looker
- You host your own, single-node (non clustered) instance
- You host your own clustered Looker but it is configured to use a shared storage directory
Syncing the New SSH Keys Directory Across Nodes
As noted above, the changes described here are only necessary if you are 1) running Looker as a cluster and 2) are not using a shared storage directory.
Also as noted above, previously-synced SSH keys will continue to function and remain in the same location (
In order to sync Git SSH deploy keys for new LookML projects, follow these steps:
- Stop the script you are using to synchronize SSH keys across nodes in the cluster.
- Identify the directory from which Looker runs (this is commonly
- Locate the portion of your existing syncing script(s) which specify the directory where SSH keys are stored. In the Looker-provided example
inotifysync_ssh.shscript, this is
- In your syncing script(s), replace the directory identified in step 3 with
/home/looker/lookerappropriately if you are running Looker from another location).
- Start your syncing script(s).