astronomer / astro-cli / bf409109-7ff7-49d3-9be4-e713f8f9994d

40%

main: 40%

Pull #2121

circleci

otto: stop setting AF_CONFIG=/dev/null when no project Airflow is detected

The previous behavior blanked af's config view in the fallback case to
keep an unrelated global current-instance from leaking in. af 0.8.0's
layered config (project-local > project-shared > global) makes that
guard counterproductive: it hides the team's committed deployment
inventory in `<project>/.astro/config.yaml` from the model, so questions
like "what DAGs are failing on staging?" hit a dead-end "no instances
configured" wall even though the user has staging defined.

Drop the sentinel. af's project-aware resolution already does the right
thing inside a project, and outside one the resolved global instance is
generally what the user wants ("the deployment I last worked on" is a
reasonable default for an open-ended question).

The remaining risk — silently picking up a stale global current-instance
when running `astro otto` from a non-project dir — is better mitigated
by surfacing the resolved instance in Otto's UI (separate change in the
otto repo) than by blanking the config.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

11 of 11 new or added lines in 1 file covered. (100.0%)

26120 of 65779 relevant lines covered (39.71%)

9.39 hits per line