This article is meant to be used in conjunction with the Looker documentation page Setting Up and Testing a Git Connection. The steps here line up with the steps in that document. This post highlights the differences when setting up version control with Atlassian’s BitBucket.
- Refer to the instructions in the Setting Up and Testing a Git Connection documentation page.
- Get the SSH URL for your BitBucket repo. The format should look like this:
- Refer to Step 3 in the Setting Up and Testing a Git Connection documentation page.
- Looker will detect your Git provider and display a deploy key for your repo. (If Looker does not successfully detect your Git provider, it will ask you to choose from a dropdown.) Select the entire Deploy Key and copy it to your clipboard, then click on the SSH Keys section of the BitBucket settings panel link to open the Users SSH keys page for your BitBucket repository.
- In the Users/Settings/SSH Keys page, click on the Add key button:
- Add a title for the deploy key. The name is not important, but you might want to include “Looker” and your project title, to keep track of it in the future.
- Paste the deploy key you copied from Looker.
- Not required for BitBucket Configuration—please see the IMPORTANT notes in Step 9 below instead.
- Click the Save button.
IMPORTANT: The deploy key MUST be saved in the SSH Keys section associated with the User, NOT in the Access Keys section associated with the repository.
IMPORTANT: The User that owns the key must be a member of the repository and must have write access to the repository. To enable write access on the repository, the user must either be the owner of the repository, have explicit write access granted to them, or be a member of a group that has write permissions on the repository.
Continue with steps in the Setting Up and Testing a Git Connection documentation page.