Home Original page

fix(deploy: exit non-zero if uncommitted changes are present by sakethsomaraju · Pull Request #2004 · astronomer/astro-cli

Description

Describe the purpose of this pull request.

Customers using GitLab or other CI/CD platforms rely on command exit codes to programmatically determine whether an astro deploy invocation succeeded or failed.

🎟 Issue(s)

Related #1721

🧪 Functional Testing

List the functional testing steps to confirm this feature or fix.
Run astro deploy with uncommitted git changes --> command fails with error and exits non-zero.

Run astro deploy -f with uncommitted changes --> deploy proceeds successfully.

Run astro deploy with a clean git state --> deploy succeeds as before.

📸 Screenshots

image

📋 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