Open andrewhlui opened 5 days ago
Hey @andrewhlui! I'm here to help you with your Docker Execution issue. I'm a bot that can assist with bugs, questions, and becoming a contributor. Let's get this sorted out together!
A similar issue was previously reported and resolved in the Cosmos repository. The issue was related to Kubernetes execution mode and was closed by a pull request that fixed the problem [1]. However, the specific details of the changes made in that pull request are not available in the provided context.
For the current issue with Docker execution mode, the DbtRunDockerOperator
does not accept the profile_config
argument in its keyword arguments. This is because the DbtRunDockerOperator
inherits from DbtDockerBaseOperator
, which in turn inherits from DockerOperator
. The constructor of DbtRunDockerOperator
is designed to pass any additional keyword arguments to its superclass, but profile_config
is not a recognized argument for these operators [2].
To work around this issue, you might consider modifying the DbtTaskGroup
or the way operator_args
are constructed to exclude profile_config
when using Docker execution mode. Alternatively, you could explore customizing the DbtRunDockerOperator
to handle profile_config
appropriately if you are willing to submit a pull request.
To continue talking to Dosu, mention @dosu.
Astronomer Cosmos Version
1.7
dbt-core version
1.8
Versions of dbt adapters
No response
LoadMode
AUTOMATIC
ExecutionMode
DOCKER
InvocationMode
None
airflow version
2.10
Operating System
Similar to #493 but for Docker.
macOS 14.6.1 (23G93)
If a you think it's an UI issue, what browsers are you seeing the problem on?
No response
Deployment
Docker-Compose
Deployment details
No response
What happened?
Docker operators don't accept
profile_config
in kwaargs. This is an issue when trying to use Docker execution mode with DbtTaskGroup, which automatically includes it.Error:
Relevant log output
How to reproduce
Anything else :)?
No response
Are you willing to submit PR?
Contact Details
No response