Skip to content

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Aug 13, 2025

When airflow package inventories cannot be downloaded (for example because they were deleted) we can always rebuild them locally from sources. This might happen for example when our "main" developer documentation published in apache-airflow-docs is accidentally or purposefully deleted (for example to refresh it from scratch).

This can also happen when we have a new provider and it has never been published, or when we add new distribution that has not yet had a documentation built (such as task-sdk, or airflowctl in the future).

This PR updates the existing mechanism to:

  • not only handle missing "apache-airflow-" packages but also the other airflow packages that do not follow this naming convention

  • adds better diagnostics so that if we miss to add a distribution in the future we know what to do


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

When airflow package inventories cannot be downloaded (for example
because they were deleted) we can always rebuild them locally from
sources. This might happen for example when our "main" developer
documentation published in `apache-airflow-docs` is accidentally
or purposefully deleted (for example to refresh it from scratch).

This can also happen when we have a new provider and it has never
been published, or when we add new distribution that has not yet
had a documentation built (such as task-sdk, or airflowctl in
the future).

This PR updates the existing mechanism to:

* not only handle missing "apache-airflow-" packages but also the
  other airflow packages that do not follow this naming convention

* adds better diagnostics so that if we miss to add a distribution
  in the future we know what to do
@potiuk
Copy link
Member Author

potiuk commented Aug 13, 2025

Handles cases like https://github.com/apache/airflow/actions/runs/16913302733/job/47921169716?pr=54406 better (self-healing basically)

@potiuk
Copy link
Member Author

potiuk commented Aug 13, 2025

mypy checks fixed separately :)

@potiuk potiuk added the backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch label Aug 13, 2025
@potiuk potiuk merged commit 8d311c7 into apache:main Aug 13, 2025
103 of 104 checks passed
@potiuk potiuk deleted the better-handling-of-airflow-inventories-missing branch August 13, 2025 14:54
github-actions bot pushed a commit that referenced this pull request Aug 13, 2025
…54464)

When airflow package inventories cannot be downloaded (for example
because they were deleted) we can always rebuild them locally from
sources. This might happen for example when our "main" developer
documentation published in `apache-airflow-docs` is accidentally
or purposefully deleted (for example to refresh it from scratch).

This can also happen when we have a new provider and it has never
been published, or when we add new distribution that has not yet
had a documentation built (such as task-sdk, or airflowctl in
the future).

This PR updates the existing mechanism to:

* not only handle missing "apache-airflow-" packages but also the
  other airflow packages that do not follow this naming convention

* adds better diagnostics so that if we miss to add a distribution
  in the future we know what to do
(cherry picked from commit 8d311c7)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
@github-actions
Copy link

Backport successfully created: v3-0-test

Status Branch Result
v3-0-test PR Link

kaxil pushed a commit that referenced this pull request Aug 13, 2025
…54464)

When airflow package inventories cannot be downloaded (for example
because they were deleted) we can always rebuild them locally from
sources. This might happen for example when our "main" developer
documentation published in `apache-airflow-docs` is accidentally
or purposefully deleted (for example to refresh it from scratch).

This can also happen when we have a new provider and it has never
been published, or when we add new distribution that has not yet
had a documentation built (such as task-sdk, or airflowctl in
the future).

This PR updates the existing mechanism to:

* not only handle missing "apache-airflow-" packages but also the
  other airflow packages that do not follow this naming convention

* adds better diagnostics so that if we miss to add a distribution
  in the future we know what to do
(cherry picked from commit 8d311c7)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk added a commit that referenced this pull request Aug 15, 2025
…54464) (#54473)

When airflow package inventories cannot be downloaded (for example
because they were deleted) we can always rebuild them locally from
sources. This might happen for example when our "main" developer
documentation published in `apache-airflow-docs` is accidentally
or purposefully deleted (for example to refresh it from scratch).

This can also happen when we have a new provider and it has never
been published, or when we add new distribution that has not yet
had a documentation built (such as task-sdk, or airflowctl in
the future).

This PR updates the existing mechanism to:

* not only handle missing "apache-airflow-" packages but also the
  other airflow packages that do not follow this naming convention

* adds better diagnostics so that if we miss to add a distribution
  in the future we know what to do
(cherry picked from commit 8d311c7)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
kaxil pushed a commit that referenced this pull request Aug 18, 2025
…54464) (#54473)

When airflow package inventories cannot be downloaded (for example
because they were deleted) we can always rebuild them locally from
sources. This might happen for example when our "main" developer
documentation published in `apache-airflow-docs` is accidentally
or purposefully deleted (for example to refresh it from scratch).

This can also happen when we have a new provider and it has never
been published, or when we add new distribution that has not yet
had a documentation built (such as task-sdk, or airflowctl in
the future).

This PR updates the existing mechanism to:

* not only handle missing "apache-airflow-" packages but also the
  other airflow packages that do not follow this naming convention

* adds better diagnostics so that if we miss to add a distribution
  in the future we know what to do
(cherry picked from commit 8d311c7)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants