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

📖 Create architecture documentation to support Airflow upgrade #6096

Closed
5 tasks
simon-pope opened this issue Nov 12, 2024 · 2 comments
Closed
5 tasks

📖 Create architecture documentation to support Airflow upgrade #6096

simon-pope opened this issue Nov 12, 2024 · 2 comments
Assignees
Labels

Comments

@simon-pope
Copy link

simon-pope commented Nov 12, 2024

User Story

As an AP team member upgrading Airflow
I need complete and agreed technical documentation for the upgrade
So that I know what is in scope for the upgrade and how it will be carried out

Value / Purpose

Technical documentation will provide the opportunity for the team to review and clarify how the Airflow upgrade will be completed
Technical documentation will allow for a clear view on what is in scope of this work, and what is not
Technical documentation will help breakdown the tasks in to sprint ready user stories

Useful Contacts

No response

User Types

No response

Hypothesis

If we have complete and signed off technical documentation for the Airflow Upgrade
Then we will improve our understanding within the team of how this will be achieved, and minimise the risks of rework and misunderstandings

Proposal

This story will cover the creation and sign off of an architecture document to support the Airflow upgrade from Airflow 2.4.3 to 2.10.x
This will include:

  • overview of the upgrade process including tasks, dependencies and indicative overall timeline
  • using SSO to provide CP with identity within Airflow
  • logging, monitoring and observability (both user facing and platform)
  • identify which tasks do not have any dependencies on users
  • exploration of opportunities within this migration to improve future work etc
  • agreement on which areas of the wider Airflow work is in scope, and what is out of scope, and a proposal/exploration on how out of scope could be delivered

Additional Information

Work complete by @jacobwoffenden - 🧪 initial local development #4

Feature Request to be included as requirement in this epic: Enable MWAA to read ECR in data-engineering-prod #5645

Definition of Done

  • Documentation provides a comprehensive overview of upgrade process
  • Documentation has been reviewed by relevant team members
  • Tasks/activities that are dependent on users are identifiable
  • Testing method, both internal and involving users, is agreed
  • Communication required to support users is understood
@simon-pope simon-pope changed the title 📖 <title> 📖 Create Documentation to support Airflow upgrade Nov 12, 2024
@YvanMOJdigital YvanMOJdigital changed the title 📖 Create Documentation to support Airflow upgrade 📖 Create architecture documentation to support Airflow upgrade Nov 21, 2024
@jacobwoffenden jacobwoffenden self-assigned this Nov 25, 2024
@jacobwoffenden
Copy link
Member

@jacobwoffenden
Copy link
Member

jacobwoffenden commented Nov 28, 2024

Request for shared services account ministryofjustice/modernisation-platform#8621

@YvanMOJdigital YvanMOJdigital moved this from 🚀 In Progress to 🎉 Done in Analytical Platform Dec 2, 2024
@YvanMOJdigital YvanMOJdigital closed this as completed by moving to 🎉 Done in Analytical Platform Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

3 participants