Alex Collins
Alex Collins
Interesting. Note - I think this may break the security model.
👋 @kevdowney we've work together I think?
We now produce SPDX with each release.
This might not be possible unfortunately. The security model of the workflow controller means it typcially cannot read configmap in the user's namespace. We would not want to change this....
```yaml apiVersion: argoproj.io/v1alpha1 kind: Workflow metadata: generateName: arguments-parameters-from-configmap- labels: workflows.argoproj.io/test: "true" annotations: workflows.argoproj.io/description: | This example demonstrates loading parameter values from configmap. Note that the "simple-parameters" ConfigMap (defined in examples/configmaps/simple-parameters-configmap.yaml)...
https://github.com/argoproj/argo-workflows/issues/6645
I’m actually not a fan of the config-map. It is quite expensive to add new items to it. It’s not amenable to Kustomize patches so not GitOps friendly. I would...
Is this a duplicate?
You should be able to use ```sh kubctl exec -ti $nodeId sh - ```
Do you mean, when you resume/stop a workflow that is complete via the Argo Server API, you get 200 OK.