Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: buckets for so-called legacy Airflow pipelines #112

Merged
merged 1 commit into from
Jul 25, 2024

Conversation

peter-woodcock
Copy link
Contributor

@peter-woodcock peter-woodcock commented Jul 25, 2024

This creates a bucket per team for Airflow pipelines, the so-called legacy pipelines that ingest into S3. This is part of the project of moving our Airflow instance out of GOV.UK PaaS which is shutting down, doing essentially a lift and shift into Data Workspace proper.

At the moment getting credentials for the bucket to the team code is slightly faffy using Terraform's "output" and then copy/pasting them into secrets manager, but it's the easiest way for now. Using roles would be "better" but would require a bit of a code change in data-flow, so leaving that to further work so we don't get blocked on it and can still migrate pipelines

@peter-woodcock peter-woodcock requested a review from a team as a code owner July 25, 2024 10:29
@michalc michalc force-pushed the feat/create-new-buckets-for-pipeline-ingest branch from 35ca6aa to eddddaa Compare July 25, 2024 12:46
@michalc michalc changed the title Draft: Create new buckets for use by pipelines in Data Workspace airflow feat: buckets for so-called legacy Airflow pipelines Jul 25, 2024
This creates a bucket per team for Airflow pipelines, the so-called legacy
pipelines that ingest into S3. This is part of the project of moving our
Airflow instance out of GOV.UK PaaS which is shutting down, doing essentially a
lift and shift into Data Workspace proper.

At the moment getting credentials for the bucket to the team code is slightly
faffy using Terraform's "output" and then copy/pasting them into secrets
manager, but it's the easiest way for now. Using roles would be "better" but
would require a bit of a code change in data-flow, so leaving that to further
work so we don't get blocked on it and can still migrate pipelines.

Co-authored-by: Mohizur Khan <[email protected]>
Co-authored-by: Peter Woodcock <[email protected]>
Co-authored-by: Michal Charemza <[email protected]>
@michalc michalc force-pushed the feat/create-new-buckets-for-pipeline-ingest branch from eddddaa to 8bb3fa8 Compare July 25, 2024 12:47
@michalc michalc merged commit 4b92c1a into main Jul 25, 2024
1 check passed
@michalc michalc deleted the feat/create-new-buckets-for-pipeline-ingest branch July 25, 2024 13:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants