bugraoz93 commented on PR #45300:
URL: https://github.com/apache/airflow/pull/45300#issuecomment-2719299572

   > Thanks for the major rework and updates. Looked at the code and this is 
okay.
   > 
   > I wanted to test interactively and failed miserably because... when 
calling `airflow auth...` it seems I need an API token. `--help` was not able 
to help me, no docs are added. Also no PR hints. Where can I (and a potential 
user in future) create an API token? Via CLI? Either I am too stupid to read, 
lost the context... or we need to add some docs such that users also would know 
how... or some more hints needed in `--help` giving hints to generate an 
API-Token. I expected to be able to pass user+password (admin/admin)...
   
   Thanks a lot for your review and comment Jens! Maybe a bit more context 
could help with these. I created this doc earlier and shared it in the dev 
call+dev channel. Please take a look if you have time. Considering deadlines 
and simplicity the decision was to pass the token to CLI which will be taken 
from the profile page. I think we should provide that but not sure we should 
include it in this huge PR or even in 3.0. I would be happy to implement that. 
I created a follow-up #47703. If you think this would be crucial for the users, 
I can try to implement it within 3.0 via including into AIP-81.
   
   
https://docs.google.com/document/d/1BSEQxKEOArPRCclfCrAjAN5hjC56vG0R5nZPc3pxF9Y/edit?usp=sharing
   I know the docs are missing for the user side. 
   
   For the documentation, I agree we should include clear guidelines on usage. 
I don't want to blow this PR more so I created a follow-up for that and already 
started working on it :) #47537 Hope this fills the gaps and addresses your 
concerns.


-- 
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