rjgoyln opened a new pull request, #71677:
URL: https://github.com/apache/airflow/pull/71677

   ## Summary
   
   The secrets tests in `test_secrets.py` and `test_configuration.py` reach for 
the amazon systems-manager and hashicorp Vault backends purely as stand-ins for 
"a custom secrets backend". Nothing there asserts anything about either one — 
the subject is core's own plumbing: how a backend is discovered, how 
`backend_kwargs` and the per-key `BACKEND_KWARG__` env vars reach its 
constructor, and what happens when it returns nothing or fails.
   
   That stand-in is what puts these tests out of reach of a core-only 
environment, and why most of them sat behind 
`skip_if_force_lowest_dependencies_marker` and never ran in the 
lowest-dependency job. The two Vault tests were worse off still: hashicorp is 
not in `airflow-core`'s dev group, so a scoped sync already failed them.
   
   Coverage is unchanged, down to an explicit JSON `null` reaching the 
instance; the connection-error path now raises on purpose rather than relying 
on a mis-shaped `hvac` mock to fail somewhere inside Vault.
   
   First slice of #71641 — cncf.kubernetes, celery, git, fab and pandas follow, 
and the dev-group entries in `airflow-core/pyproject.toml` come out once 
nothing needs them.
   
   ## Tests
   
   Both files pass in a full workspace. In an environment built with `uv sync 
--project airflow-core` minus the six dev-group providers, the amazon and 
hashicorp failures are gone; the eight that remain are the celery 
provider-config tests a later slice covers.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 5)
   
   Generated-by: Claude Code (Opus 5) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to