[Bug]: --env CLI flag parses value with = in them incorrectly

[plungingChode]

What happened?

I tried to pass an environment variable with a value similar to A=B.

stepci --env 'env=A=B`

The variable was parsed as

{ env: "A" }

What did you expect to happen?

It should have been parsed as

{ env: "A=B" }

Version

2.6.8

Environment

Node v16.20.0

How can we reproduce this bug?

Run stepci --env 'env=A=B'

Relevant log output

No response

Would you be interested in working on a bugfix for this issue?

• Yes! Assign me

[mishushakov]

Have you tried the below:

stepci -e 'A=B`

[sebastianwis]

Hey @plungingChode
Thanks for creating the issue! Would you mind joining our Discord?
https://discord.com/invite/KqJJzJ3BTu

Would love to hear from you!

[plungingChode]

Have you tried the below:

stepci -e 'A=B`

Hi! Yes, but my issue is that if an environment variable passed as a CLI argument contains an equals sign (for some reason), anything after the second = is completely ignored. What I'd expect is for

stepci -e 'var=A=B'

to be available to use in the workflow as ${{env.var}}, having the value A=B. Instead, it is just parsed as A. If this is intended, please feel free to close the issue.

[sebastianwis]

Hi @plungingChode
Thank you for your contribution here!
It would be amazing to welcome you to our Discord if you haven't joined it yet:
https://discord.com/invite/KqJJzJ3BTu
This is where we keep users up to date with updates, features and bug resolutions.