potiuk commented on PR #50057:
URL: https://github.com/apache/airflow/pull/50057#issuecomment-2843468843

   Few things that this PR leverages from our existing framework for provider's 
capabiliy discovery:
   
   * `airflow providers queues` CLI - showing automatically all message queues 
discovered from the "get_provider_info" extension points of installed providers:
   
   
![image](https://github.com/user-attachments/assets/7593b027-fe92-4502-974b-907b30847362)
   
   * Added "Core concept" page describing Message Queue concept:
   
   
![image](https://github.com/user-attachments/assets/c2ce8fcd-ba16-46a6-b1a0-9a9205eae9d2)
   
   * Added Summary Page in providers summary doc - with summary of all 
autoamaticaly discovered message queues from provider.yaml
   
   
![image](https://github.com/user-attachments/assets/dfebd998-f3c0-4909-b48b-f2f49db5f796)
   
   
   * Added Message Queuees on the ist of `core extensions`:
   
   
![image](https://github.com/user-attachments/assets/2053e65a-9ba6-407b-8e20-7e8048a9c65a)
   
   
   All that comes out-of-the-box after tapping-in the standard provider's 
discovery mechanism,
   
   
   BTW. The new `uv run --group doc build-docs --autobuild` workflow is 
**FANTASTIC** - I really started to like editing docuementation, it likely 
speeds up documentation iteration more than order of magnitude. I was able to 
modify and move things around super-quickly  and preview things while they are 
changed, see the errors in generated documentation when there were errors etc.
   
   
   And I would really appreciate some suggestions (or even fixups) to the 
documentation I created. I slapped things together quickly from AIP-82 and few 
other places, but I am pretty sure we can do way better and more "catchy" 
description - maybe even add some images from the AIP-82 design etc.  
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to