For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
      • AstroFully-managed data operations, powered by Apache Airflow.
      • Astro Private CloudRun Airflow-as-a-service in your environment.
      • Professional ServicesExpert Airflow services for your enterprise's success.
    • Tools
      • Cosmos
      • Orbiter
      • CLI
      • AI SDK
      • Agents
      • Blueprint
      • UpdatesThe State of Airflow 2026See the insights from over 5,800 data practitioners in the full report. Download Now ➔
  • Customers
  • Docs
    • Insights
      • Blog
      • Webinars
      • Resource Library
      • Events
    • Education
      • Academy
      • What is Airflow?
  • Pricing
Get Started Free
  • Astro API v1
    • Overview
    • Get started
    • Versioning and support
    • Migrate to v1
    • Deploy with the API
  • API Reference
    • Changelog
    • Book Office Hours

Product

  • Platform Overview
  • Astro
  • Astro Observe
  • Astro Private Cloud
  • Security & Trust
  • Pricing

Tools & Services

  • Cosmos
  • Docs
  • Professional Services
  • Product Updates

Use Cases

  • AI Ops
  • Data Observability
  • ETL/ELT
  • ML Ops
  • Operational Analytics
  • All Use Cases

Industries

  • Financial Services
  • Gaming
  • Retail
  • Manufacturing
  • Healthcare
  • All Industries

Resources

  • Academy
  • eBooks & Guides
  • Blog
  • Webinars
  • Events
  • The Data Flowcast Podcast
  • All Resources

Airflow

  • What is Airflow
  • Airflow on Astro
  • Airflow 3.0
  • Airflow Upgrades
  • Airflow Use Cases
  • Airflow 2.x End of Life

Company

  • Our Story
  • Customers
  • Newsroom
  • Careers
  • Contact

Support

  • Knowledge Base
  • Status
  • Contact Support
GitHubYouTubeLinkedInx
  • Legal
  • Privacy
  • Terms of Service
  • Consent Preferences

  • Do Not Sell or Share My Personal information
  • Limit the Use Of My Sensitive Personal Information

Apache Airflow®, Airflow, and the Airflow logo are trademarks of the Apache Software Foundation. Copyright © Astronomer 2026. All rights reserved.

LogoLogo

Changelog

April 22, 2026
April 22, 2026
Was this page helpful?
Previous

April 2, 2026

Next
Built with

Summary

  • Create Deployment requests now require only name and workspaceId. The server resolves infrastructure from Workspace defaults (or auto-selects when the Organization has a single non-shared cluster), infers the Deployment type from the resolved cluster, and applies defaults for runtime version, executor, scheduler size, and related fields. This reduces the create Deployment API from roughly 15 required fields down to 2.
  • Added defaultClusterId, defaultCloudProvider, and defaultRegion on Workspace so Workspace admins can pre-configure target infrastructure for new Deployments. defaultClusterId is mutually exclusive with defaultCloudProvider and defaultRegion.
  • Added GET /organizations/{organizationId}/deployments/{deploymentId}/logs and GET /users/self endpoints.
  • Added hasAllowedIpAddressRanges and shouldEnforceDedicatedClusters as required properties on the Organization schema.
  • Added workspaceId and deploymentId filters to GET /organizations/{organizationId}/teams.

Added

  • Endpoints

    • GET /organizations/{organizationId}/deployments/{deploymentId}/logs: Get logs for an Astro Deployment. Supports filtering by log source (scheduler, triggerer, worker, webserver, dag-processor, apiserver), time range, text search, and pagination.
    • GET /users/self: Get the authenticated user’s profile, roles, invites, and feature flags. Supports an optional createIfNotExist query parameter.
  • Schemas

    • CreateDeploymentInstanceSpecRequest
      • au: Integer. Astro unit allocation for the Deployment pod. Minimum 5, maximum 24. Optional.
      • replicas: Integer. Number of pod replicas. Minimum 1, maximum 4. Optional.
    • UpdateDeploymentInstanceSpecRequest
      • au: Integer. Astro unit allocation for the Deployment pod. Minimum 5, maximum 24. Required.
      • replicas: Integer. Number of pod replicas. Minimum 1, maximum 4. Required.
    • DeploymentLog
      • Required: limit, maxNumResults, offset, resultCount, results, searchId.
      • results: Array of DeploymentLogEntry.
    • DeploymentLogEntry
      • Required: raw (string), source (enum: scheduler, webserver, triggerer, worker, dag-processor, apiserver), timestamp (number).
    • SelfUser
      • Required: avatarUrl, createdAt, fullName, id, status, updatedAt, username.
      • Also includes featureFlags, invites, isIdpManaged, organizationId, and roles.
    • SelfUserFeatureFlag, SelfUserInvite, SelfUserRole, SelfUserRoleScope: Supporting schemas for SelfUser.
    • UpdateWorkerQueueRequest: Used by the workerQueues array on UpdateDedicatedDeploymentRequest, UpdateHybridDeploymentRequest, and UpdateStandardDeploymentRequest. Required fields: isDefault, maxWorkerCount, minWorkerCount, name, workerConcurrency.
  • Properties

    • CreateWorkspaceRequest and UpdateWorkspaceRequest: defaultCloudProvider (enum: AWS, AZURE, GCP), defaultClusterId, and defaultRegion. Workspace admins use these fields to pre-configure target infrastructure for new Deployments. When a create Deployment request omits clusterId, cloudProvider, and region, the server uses these Workspace defaults. defaultClusterId is mutually exclusive with defaultCloudProvider and defaultRegion.
    • Organization: hasAllowedIpAddressRanges (boolean, required) indicating whether the Organization has at least one allowed IP address range configured, and shouldEnforceDedicatedClusters (boolean, required).
    • UpdateOrganizationRequest: shouldEnforceDedicatedClusters (boolean).
    • Workspace: defaultCloudProvider, defaultClusterId, and defaultRegion (strings) reflecting the configured defaults.
  • Query parameters

    • GET /organizations/{organizationId}/teams: workspaceId and deploymentId filter the response to Teams with a role in the specified Workspace or Deployment.

Changed

  • Removed required fields on create Deployment requests. When a field is omitted, the server applies a default. The only remaining required fields are name and workspaceId.