kunaljubce commented on code in PR #46664:
URL: https://github.com/apache/airflow/pull/46664#discussion_r1957255251
##########
dev/breeze/src/airflow_breeze/commands/developer_commands.py:
##########
@@ -1149,3 +1151,36 @@ def autogenerate(
cmd = f"/opt/airflow/scripts/in_container/run_generate_migration.sh
'{message}'"
execute_command_in_shell(shell_params, project_name="db", command=cmd)
fix_ownership_using_docker()
+
+
[email protected](name="doctor", help="Troubleshoot breeze")
[email protected](
+ "--project-name",
+ help="Name of the docker-compose project to bring down. "
+ "The `docker-compose` is for legacy breeze project name and you can use "
Review Comment:
@potiuk So the way I am thinking of this, if we are supporting legacy
project names to be passed as a parameter to `breeze down`, we should also have
the same capability to handle this parameter in `breeze doctor`. Lemme know if
you're not in agreement here.
One thing that I am changing here is, reusing the `@option_project_name`
decorator from `airflow_breeze.commands.common_options` as is done with `breeze
down`.
--
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]
