Skip to content

Comments

Support reading env objs without settings file#1914

Merged
jeremybeard merged 1 commit intomainfrom
support-env-objs-wo-settings-file
Aug 14, 2025
Merged

Support reading env objs without settings file#1914
jeremybeard merged 1 commit intomainfrom
support-env-objs-wo-settings-file

Conversation

@jeremybeard
Copy link
Contributor

Description

This change fixes a confusing behavior where the CLI will silently not load connections from the specified Astro deployment or workspace if the CLI settings file (default airflow_settings.yaml) is not present. The new behavior is to read Astro connections regardless of whether the settings file is present.

🧪 Functional Testing

  • Unit tests added
  • Manually tested locally

📋 Checklist

  • Rebased from the main (or release if patching) branch (before testing)
  • Ran make test before taking out of draft
  • Ran make lint before taking out of draft
  • Added/updated applicable tests
  • Tested against Astro-API (if necessary).
  • Tested against Houston-API and Astronomer (if necessary).
  • Communicated to/tagged owners of respective clients potentially impacted by these changes.
  • Updated any related documentation

@jeremybeard jeremybeard merged commit 41c3df1 into main Aug 14, 2025
3 of 5 checks passed
@jeremybeard jeremybeard deleted the support-env-objs-wo-settings-file branch August 14, 2025 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants