Skip to content

Fix SBOM commands to work for Airflow 2 #52591

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

Merged
merged 1 commit into from
Jun 30, 2025
Merged

Conversation

potiuk
Copy link
Member

@potiuk potiuk commented Jun 30, 2025

Airflow 3 will need to be updated with package-json.lock but for now we are fixing the sbom command to work for Airflow 2 (and generate airflow 2.11 SBOMS.

Changes:

  • passing --github-token parameter which might be helpful to not rate-limit GitHub calls

  • allowing to pass either --airflow-site-archive-path or --airflow-root-path depending where we want to generate sbom - it can be generated in archive folder directly (when we want to update historical data) or in the airflow source directory when we want to add SBOM to just generated documentation during the doc-building phase


^ 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.

Airflow 3 will need to be updated with package-json.lock but for now
we are fixing the sbom command to work for Airflow 2 (and generate
airflow 2.11 SBOMS.

Changes:

* passing --github-token parameter which might be helpful to not
  rate-limit GitHub calls

* allowing to pass either `--airflow-site-archive-path` or
  `--airflow-root-path` depending where we want to generate sbom -
  it can be generated in `archive` folder directly (when we want
  to update historical data) or in the airflow source directory
  when we want to add SBOM to **just** generated documentation
  during the doc-building phase
@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-0-test Mark PR with this label to backport to v3-0-test branch labels Jun 30, 2025
@potiuk potiuk changed the title Fix SBOM commands to work for Airfow 2 Fix SBOM commands to work for Airflow 2 Jun 30, 2025
@potiuk potiuk merged commit acea31e into apache:main Jun 30, 2025
193 of 194 checks passed
@potiuk potiuk deleted the fix-sbom-commands branch June 30, 2025 21:25
github-actions bot pushed a commit that referenced this pull request Jun 30, 2025
Airflow 3 will need to be updated with package-json.lock but for now
we are fixing the sbom command to work for Airflow 2 (and generate
airflow 2.11 SBOMS.

Changes:

* passing --github-token parameter which might be helpful to not
  rate-limit GitHub calls

* allowing to pass either `--airflow-site-archive-path` or
  `--airflow-root-path` depending where we want to generate sbom -
  it can be generated in `archive` folder directly (when we want
  to update historical data) or in the airflow source directory
  when we want to add SBOM to **just** generated documentation
  during the doc-building phase
(cherry picked from commit acea31e)

Co-authored-by: Jarek Potiuk <[email protected]>
Copy link

Backport successfully created: v3-0-test

Status Branch Result
v3-0-test PR Link

@gopidesupavan
Copy link
Member

thank you :)

github-actions bot pushed a commit to aws-mwaa/upstream-to-airflow that referenced this pull request Jun 30, 2025
Airflow 3 will need to be updated with package-json.lock but for now
we are fixing the sbom command to work for Airflow 2 (and generate
airflow 2.11 SBOMS.

Changes:

* passing --github-token parameter which might be helpful to not
  rate-limit GitHub calls

* allowing to pass either `--airflow-site-archive-path` or
  `--airflow-root-path` depending where we want to generate sbom -
  it can be generated in `archive` folder directly (when we want
  to update historical data) or in the airflow source directory
  when we want to add SBOM to **just** generated documentation
  during the doc-building phase
(cherry picked from commit acea31e)

Co-authored-by: Jarek Potiuk <[email protected]>
potiuk added a commit that referenced this pull request Jun 30, 2025
Airflow 3 will need to be updated with package-json.lock but for now
we are fixing the sbom command to work for Airflow 2 (and generate
airflow 2.11 SBOMS.

Changes:

* passing --github-token parameter which might be helpful to not
  rate-limit GitHub calls

* allowing to pass either `--airflow-site-archive-path` or
  `--airflow-root-path` depending where we want to generate sbom -
  it can be generated in `archive` folder directly (when we want
  to update historical data) or in the airflow source directory
  when we want to add SBOM to **just** generated documentation
  during the doc-building phase
(cherry picked from commit acea31e)

Co-authored-by: Jarek Potiuk <[email protected]>
Copy link
Contributor

@amoghrajesh amoghrajesh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:dev-tools backport-to-v3-0-test Mark PR with this label to backport to v3-0-test branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants