Alex Collins
Alex Collins
I think the UI is looking at `workflow.spec` be should look at `workflow.status.storeWorkflowSpec`. We'd need to hunt down where that is.
This is where this needs to be fixed: https://github.com/argoproj/argo-workflows/blob/dbda60fc5c72c02729d98b4e5ff08f89a6bf428c/ui/src/app/workflow-event-bindings/components/workflow-event-bindings/workflow-event-bindings.tsx#L109 Should be like this: https://github.com/argoproj/argo-workflows/blob/master/ui/src/app/apidocs/components/apiDocs.tsx#L10 Would you like to submit a PR? We can set you up with a mentor to...
@basanthjenuhb ?
So we're saying they cannot be supported. We should probabyl document that.
I don't think we should fix this. @juliev0 work will deprecate this endpoint. Users should move to use the next endpoint. We could put a 301 redirect in place
The current endpoints don't container the namespace in the URL, so we cannot use GetNamespace to perform namespaced RBAC on them. The current endpoints don't support directories. I'd like to...
I’m not a lawyer. The email is logged for audit purposes. The email is not a customer’s email, it would be that of Argo operator’s employee. It would be helpful...
OK. We can remove this logging. Could you submit a PR?
Can you please clarify what you mean by "workflow stopped"? Do you mean you ran "argo stop my-wf"?
@isubasinghe @uday-mandava please make sure you do NOT use Kubernetes events for any automation, they are not reliable: https://blog.argoproj.io/maybe-dont-use-kubernetes-events-for-automation-53951bdfd602