Skip to content

docs: clarify AssetAlias usage with detailed explanation and examples #52259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

nrnavaneet
Copy link

This PR improves the documentation for AssetAlias in the authoring and scheduling assets guide.

  • Adds a clear introduction explaining what AssetAlias is and why it’s useful.
  • Provides step-by-step usage instructions for emitting asset events via outlet_events and Metadata.
  • Includes code examples with detailed comments for better understanding.
  • Clarifies behavior when using multiple aliases and event deduplication.
  • Adds guidance on consuming asset events from aliases in downstream tasks.

These improvements aim to help users better understand and effectively use AssetAlias for dynamic asset management and DAG dependency configuration.

Closes issue [52250]

nrnavaneet and others added 3 commits June 25, 2025 04:10
- Added a note under "Using Airflow Public Interfaces" to recommend using `airflow.sdk` as the official interface from Airflow 3.0.
- Referenced AIP-72 and linked related documentation.
- Encouraged users to prefer REST API and Python Client for integrations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant