Added the support for clusterID for the runtime releases flows in CLI by rujhan-arora-astronomer · Pull Request #1906 · astronomer/astro-cli

Description

Currently, the CLI fetches the list of available Runtime versions and applies filters based on the Houston configmap. This approach is problematic for 1.0 because it doesn't account for feature flags or specific configurations that may be enabled on a per-cluster basis.

As a result, a user might see a list of Runtimes that is not accurate for their target environment. For example, a cluster with a feature flag enabled for Airflow 3 would not see it in the list of available versions if it is disabled at the global level, preventing them from using it.
This PR resolves this issue by ensuring that whenever the CLI requests a list of available Runtime versions, it passes the relevant clusterId ID. The backend API can then use this ID to evaluate cluster-specific feature flags and return a precise, filtered list of Runtimes that are actually available for that cluster.

🎟 Issue(s)

Related 7572(https://github.com/astronomer/issues/issues/7572)

🧪 Functional Testing

Tested locally
Unit tests

📸 Screenshots

Screenshot 2025-07-31 at 1 30 42 PM Screenshot 2025-07-31 at 1 30 18 PM Screenshot 2025-07-31 at 1 29 58 PM Screenshot 2025-07-31 at 1 18 30 PM Screenshot 2025-07-31 at 1 11 54 PM Screenshot 2025-07-31 at 1 11 19 PM

📋 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