gp env - fails when value contains a space or newline

[shaal]

Bug description

After the fix for #4493 was deployed to production, it introduced a new bug.
Now when the value contains space character, gp env fails.

Steps to reproduce

Open any Gitpod workspace.
In terminal, type:
gp env message="hello world"

empty string (correct format is key=value)

Compare it with a regular environment variable that doesn't have this issue:

1. export message="hello world"
2. echo $message
3. Confirm the result is hello world

Expected behavior

gp env should allow the same values that Bash's export does.

Here's how I want to use it, but now it is broken :(

ssh-keygen -q -t rsa -b 4096 -f ~/.ssh/id_rsa
gp env MY_SSH_KEY=$(cat ~/.ssh/id_rsa)

Example repository

No response

Anything else?

No response

[shaal]

I ran some additional tests, trying to overcome the bug that doesn't allow spaces. When I figured out how to bypass spaces issues, I realized now gp env doesn't allow me to add newlines.

To clarify - this bug was introduced after #4494 was deployed. Before that, only = was causing a problem, spaces and newlines worked fine.

My repo (https://github.com/shaal/drupalpod) is broken because of this bug 😞
I use it for a one-time setup that saves data, and future workspace automatically reading that data using gp env.

I didn't discover the bug earlier because I didn't know that it was deployed (I could only track the PR that fixed it when it got merged to main)

I'd like to ask to test the PR that is going to fix this issue when it's ready.