You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/01/27 03:21:44 UTC

[GitHub] [airflow] Bowrna edited a comment on issue #20960: Breeze: Enter Shell environment with Breeze

Bowrna edited a comment on issue #20960:
URL: https://github.com/apache/airflow/issues/20960#issuecomment-1022797006


   initialization::create_directories()
     Creates folders to mount inside the container. 
   initialization::check_docker_version()
    
   This checks the docker version and instructs if failed to install docker. Check if the docker available is good to go
   
   build_images::forget_last_answer()
   To remove the forced answer given previously. 
   
   build_images::determine_docker_cache_strategy()
   We use pulled docker image cache by default for CI images 
   
   build_images::rebuild_ci_image_if_needed()
   Checks if rebuild CI image is needed or not. Checks if docker build is needed. If yes, confirms image rebuild.
   
   breeze::print_badge()
   
   This emits the airflow logo, backend(mysql, postgres etc), backend_version, checks the cache to see if we have to suppress the asciiart logo. If not, print the visual art for airflow
   
   initialization::summarize_build_environment()
   
   How do we get values for all env variables initialized here? Are all of them are constants or do we have to compute on-demand or pass as a param? I will have to verify this part.
   
   breeze::print_setup_instructions()
   Prints setup instruction in case we find that autocomplete is not set
   
   
   resoure_check() in run_resource_check.py
   
   breeze::prepare_command_file()
   	This generates script inside build_cache dir depending on the type of configuration chosen and env var for breeze and file that can be run to use the docker command.
   	
   @potiuk I tried to find the logical steps getting executed in entering the shell. Please correct me if any of my understanding is wrong. 
   


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org