inputs.parameters not exist in ARGO_TEMPLATE env var

[Oscourse1245]

Pre-requisites

• I have double-checked my configuration
• I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
• I have searched existing issues and could not find a match for this bug
• I'd like to contribute the fix myself (see contributing guide)

What happened? What did you expect to happen?

when upgrading from 3.5.8 to v3.6.0, I saw that in the ARGO_TRMPLATE env var, the inputs.parametes is missing.

Version(s)

v3.6.0

Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.

any workflow

Logs from the workflow controller

I have private info in the controller log

Logs from in your workflow's wait container

same as above

[jswxstw]

It is by design, please see the ChangeLog:

• bf7760a46 feat: ARGO_TEMPLATE env var without inputs.parameters (feat: ARGO_TEMPLATE env var without inputs.parameters #13742)
• c9b1477fd refactor: Only set ARGO_TEMPLATE env for init container. (refactor: Only set ARGO_TEMPLATE env for init container. #13761)

[Oscourse1245]

I see, but the env var ARGO_TEMPLATE_WITH_INPUTS_PARAMETERS is removed and I don't have the ability to add the inputs.parameters by the controller configuration.
Am I wrong?

[jswxstw]

I see, but the env var ARGO_TEMPLATE_WITH_INPUTS_PARAMETERS is removed and I don't have the ability to add the inputs.parameters by the controller configuration.

ARGO_TEMPLATE_WITH_INPUTS_PARAMETERS is removed in #13761, which is based on this consideration: #13761 (comment)

[Oscourse1245]

Can I configure the controller to add the inputs.parameters to ARGO_TEMPLATE env var?

[jswxstw]

Sorry, but this is no longer supported. By the way, may I ask why you are relying on inputs.parameters in ARGO_TEMPLATE?

[Oscourse1245]

we are using the any parameters after they resolved, the ARGO_TEMPLATE contain them, we are resubmitting the specific template after some adjustment.
do you think we can get the resolved parameters in other way?

[jswxstw]

Shouldn't the parameters be passed to the container args?

[Oscourse1245]

Yes, I am getting the parameters, but I asked for better way to resolve it, instead of parse any parameter one by one.

[jswxstw]

Variable inputs.parameters contains all input parameters to a template as a JSON string.