bug: wmill sync push command does'nt push the env variables included in the runtime settings of any script

[Jesshuan]

Describe the bug

Hey the windmill team !...

(with the wmill CLI version : 1.589.3
& the windmill image version :v1.592.0)

One of the issues met during my "custom benchmark" ;)...
There aren't many.

Let's suppose i have an existing project with an existing script with env variables defined (as code) in the 'env' settings like that :

summary: task1_delete_s3_scenar_2_bash_python_script
description: A simple bash script for the benchmark scenario 2 variant 1 with bash script
lock: ''
envs:

• PYTHONPATH=/tmp/windmill/cache/python_3.12/global-site-packages:${PYTHONPATH}
• 'MINIO_ENDPOINT=http://minio.external-db.svc.cluster.local:9000'
• MINIO_ACCESS_KEY=minioadmin
• MINIO_SECRET_KEY=minioadmin
• OUTPUT_BUCKET=output-data

• PUSHGATEWAY_URL=http://observability-stack-prometheus-pushgateway.observ-stack.svc.cluster.local:9091
• PG_HOST=postgres.external-db.svc.cluster.local
• PG_DB=benchmark
• PG_USER=benchmark
• PG_PASSWORD=benchmark
• OUTPUT_KEY=not_used
  kind: script
  schema:
  $schema: 'https://json-schema.org/draft/2020-12/schema'
  type: object
  [...]

Now, when i use the wmill CLI with "wmill sync push" command,
i would expect to retrieve these env variables in the settings -> Runtime -> Custom Env variables of the script.

but just the 'wmill sync pull' command does the sync, not the 'push' command.

I've searched what could be the "--include" option that's i would have to add within my wmill cli command... (live "--include-schedules", etc.) but it seems this "env" argument doesn't exist.

To reproduce

1. On a existing workspace, create a bash or python script.
2. Add to it some arbitrary env variables within the "settings -> Runtime -> Custom env variables" section.
3. From the terminal, on the dedicated project, "wmill sync pull" command, to retrieve this new content.
4. On a the script itself, add additional env variables in the 'envs' section of the yaml associated with the script.
5. "wmill sync push" command to push this new content on the workspace.
6. Look at the script from the UI. Go back to the "settings -> Runtime -> Custom env variables" section. Your additionnal env variables created "as code" are missing...

Note: From the terminal, when you try “wmill sync push” several times, you should see the diff lines of code several times as well, as if the new content was never updated...

Expected behavior

wmill sync push command should allow to retrieve the env variables defined as-code within a script yaml definition.

Screenshots

No response

Browser information

No response

Application version

windmill image version :v1.592.0, wmill CLI version : 1.589.3

Additional Context

No response

[rubenfiszel]

Should be fixed in CLI 1.623.0