Guillaume Onfroy comments

Results 40 comments of


                                            Guillaume Onfroy

`inputs` or `workflow` is nil when used in sprig expression that has more than 1 parameter (`withParam` loop)

@alexec What about the original issue?

`inputs` or `workflow` is nil when used in sprig expression that has more than 1 parameter (`withParam` loop)

@alexec You mean the original post is unclear?

`inputs` or `workflow` is nil when used in sprig expression that has more than 1 parameter (`withParam` loop)

The gist is, considering the following workflow: ```yaml --- apiVersion: argoproj.io/v1alpha1 kind: WorkflowTemplate metadata: name: my-template namespace: argo spec: entrypoint: execute arguments: parameters: - name: X value: xxx - name:...

`inputs` or `workflow` is nil when used in sprig expression that has more than 1 parameter (`withParam` loop)

@alexec Would you confirm that looks like a bug to you?

`inputs` or `workflow` is nil when used in sprig expression that has more than 1 parameter (`withParam` loop)

> This might be a long shot, but @aaaaahaaaaa and @rocketspacer, could you try using `workflow.parameters['message']` instead of `workflow.parameters.message`? Already tried. Same outcome.

`inputs` or `workflow` is nil when used in sprig expression that has more than 1 parameter (`withParam` loop)

Support multiple standards to parse on `dataFrom`

Yes technically. But perhaps it would be nice to relax a bit the validation since this has been working for years. When uploading JSON files to secret stores, or pasting...

Support multiple standards to parse on `dataFrom`

I assume you won't consider this so we'll update our secrets.

CREATE EXTENSION pgmq fails in Postgres 17.6.1.016+ due to function overload handling bug in after-create script

This is not only breaking the installation via the SQL statement but also via the UI

CREATE EXTENSION pgmq fails in Postgres 17.6.1.016+ due to function overload handling bug in after-create script

I had to downgrade the CLI all the way to version `2.49` to be able to install the extension locally.