[GitHub] [airflow] edithturn commented on issue #23085: Breeze: Running K8S tests with Kind with Breeze

Mon, 09 May 2022 20:35:57 -0700 


edithturn commented on issue #23085:
URL: https://github.com/apache/airflow/issues/23085#issuecomment-1121849684

   @potiuk let me know if I am going for the right path:
   
   1. In the Developer tools section, I am adding kind-cluster as a command 
(./breeze --help)
   
   ![Screenshot from 2022-05-09 
22-22-48](https://user-images.githubusercontent.com/58795858/167537308-2c695e72-d67a-45f1-bf7f-24977e237ed3.png)
   
   * As options of kind-cluster, I am adding just for now "start", "stop" and 
"restart". 
   
   ![Screenshot from 2022-05-09 
22-22-59](https://user-images.githubusercontent.com/58795858/167537334-491e4f73-ed52-428e-a2b2-ed4fd7f64333.png)
   
   2.  I added a new class in 
`dev/breeze/src/airflow_breeze/utils/kind_command_utils.py`, it will contain 
validations to start/stop...etc kind with airflow version for this: 
`./breeze-legacy kind-cluster start`
   
   ![Screenshot from 2022-05-09 
22-28-06](https://user-images.githubusercontent.com/58795858/167537193-28c8437a-47cf-41d6-adaa-e8a788c727c3.png)
   
   Now, --start, --stop, --restart, should they be commands and not options, 
right? In `./breeze kind-cluster start`  <-- kind-cluster is a command and 
**start** should be a command too


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