Open menzenski opened 1 year ago
Is your feature request related to a problem? Please describe.
We run dbt-core (within Meltano - see https://github.com/elementary-data/elementary/issues/1160 ) using Argo Workflows. Per https://docs.elementary-data.com/deployment-and-configuration/collect-job-data#cant-find-your-orchestrator-missing-info I'm opening this issue because elementary doesn't currently support an Argo Workflows orchestrator.
Describe the solution you'd like
It would be great to have Argo Workflows metadata captured in the same orchestrator metadata model as others:
Orchestrator name: argo_workflows Job name: job_name (Argo Workflows name) Job ID: n/a ? Job results URL: n/a ? The ID of a specific run execution: job_run_id (Argo Workflows uid ) Job run results URL: n/a ?
argo_workflows
name
uid
Describe alternatives you've considered not sure
Additional context
Would you be willing to contribute this feature? Yes!
It seems to be possible to pass Argo Workflows orchestrator information today:
dbt run --select elementary --vars '{orchestrator: "Argo Workflows", job_id: "{{workflow.name}}", job_run_id: "{{workflow.uid}}"}'
Is your feature request related to a problem? Please describe.
We run dbt-core (within Meltano - see https://github.com/elementary-data/elementary/issues/1160 ) using Argo Workflows. Per https://docs.elementary-data.com/deployment-and-configuration/collect-job-data#cant-find-your-orchestrator-missing-info I'm opening this issue because elementary doesn't currently support an Argo Workflows orchestrator.
Describe the solution you'd like
It would be great to have Argo Workflows metadata captured in the same orchestrator metadata model as others:
Orchestrator name:
argo_workflows
Job name: job_name (Argo Workflowsname
) Job ID: n/a ? Job results URL: n/a ? The ID of a specific run execution: job_run_id (Argo Workflowsuid
) Job run results URL: n/a ?Describe alternatives you've considered not sure
Additional context
Would you be willing to contribute this feature? Yes!