No description
This repository has been archived on 2026-04-20. You can view files and clone it, but you cannot make any changes to its state, such as pushing and creating new issues, pull requests or comments.
Find a file
Chris Pressland cdb1d19eb3
Some checks failed
tests / test (push) Failing after 6s
upload / upload (push) Failing after 7s
Added Airbyte install support
2022-03-18 00:10:57 +00:00
.github/workflows Added CI 2022-02-05 15:34:58 +00:00
recipes Added Airbyte install support 2022-03-18 00:10:57 +00:00
templates Final set of cert fixes... hopefully! 2022-03-14 19:44:21 +00:00
test/integration Initial commit 2022-02-01 20:36:12 +00:00
.gitignore Added Airbyte install support 2022-03-18 00:10:57 +00:00
Berksfile Initial commit 2022-02-01 20:36:12 +00:00
Berksfile.lock Added Airbyte install support 2022-03-18 00:10:57 +00:00
chefignore Initial commit 2022-02-01 20:36:12 +00:00
kitchen.yml Initial commit 2022-02-01 20:36:12 +00:00
metadata.rb Added Airbyte install support 2022-03-18 00:10:57 +00:00
README.md Added Airbyte install support 2022-03-18 00:10:57 +00:00

cookbook-ultron

Deploys ClickHouse and prepares server for an AirByte deployment (kicked off manually by DevOps, see below)

Clickhouse

Deploys ClickHouse using config file found in ./templates/config

AirByte

Due to AirByte not supporting a sane deployment method, docker-compose is required for deployment, due to time constraints this will remain a manual deployment step but be well documented in this README.md file.

Installation Steps

Following the installation of ClickHouse, Docker and docker-compose will be installed.

AirBytes Git Repo will be cloned to /opt/airbyte and kept up to date on each Chef Run, this is a reletively expensive operation but the documentation suggests this is the recommended method.

The Application should be launched, manually, using docker-compose up -d from the cloned directory. This will need to be tested to confirm it survives server restarts.


NOTE

Monitoring of AirByte will be critical to the success of this application. We need to figure out a good method for determining application availability.

Due to DockerHub limits, rate limiting COULD occur, hopefully not, but be mindful. If it does, you'll just have to wait a few hours and retry.