Open ghulevishal opened 1 year ago
Based on initial triage. GlobalArtifacts
are not included in the scope to replace/substitute for the exit handler. Scope should populate the globalartifacts
https://github.com/argoproj/argo-workflows/blob/f5e31f8f36b32883087f783cb1227490bbe36bbd/workflow/controller/operator.go#L3081
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Any update on this?
An issue related to this one: the global output variables cannot be accessed in in exit handler either. Argo complains that {{workflow.outputs.parameters.global_variable_name}}
cannot be resolved.
Facing same issue as @Luobiny , are there any estimations to when this will be solved?
Pre-requisites
:latest
What happened/what you expected to happen?
Whenever we are calling the global output artifact in the exithandler Its failing with the error:
Bad Request: templates.exit-handler.steps failed to resolve
{{workflow.outputs.artifacts.output-result-car}}
This error was introduced after upgrading to the v3.4.6,. Also have tested with v3.4.7, v3.4.8, v3.4.9, v3.4.10 same issue persist.
After downgrading to v3.4.5 same workflow is working without any issue
Version
v3.4.6
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
Logs from in your workflow's wait container