Skip to content

Support multiline environment variables #2058

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ceefour opened this issue Oct 25, 2020 · 7 comments
Open

Support multiline environment variables #2058

ceefour opened this issue Oct 25, 2020 · 7 comments
Labels
component: dashboard meta: never-stale This issue can never become stale team: webapp Issue belongs to the WebApp team type: feature request New feature or request

Comments

@ceefour
Copy link

ceefour commented Oct 25, 2020

Describe the bug

Multiline environment variable is not working properly

Steps to reproduce

  1. Go to https://gitpod.io/settings/
  2. Set a multiline environment variable, e.g. JWT_PUBLIC_KEY (PEM encoded)

Expected behavior

  • UI is showing the value correctly
  • Value is passed to environment correctly

Additional information

Applies to any workspace.

Example repository

Applies to any workspace.
@corneliusludmann
Copy link
Contributor

Thanks for the report. Currently, we don't support multiline env vars. You could use base64 encoding and a startup command as a workaround.

@corneliusludmann corneliusludmann added the type: feature request New feature or request label Oct 26, 2020
@ceefour
Copy link
Author

ceefour commented Oct 26, 2020

Yes, so I think this becomes a feature request.

@ceefour ceefour changed the title Multiline environment variable is not working properly Support multiline environment variables Oct 26, 2020
@fullmetalrooster
Copy link
Contributor

fullmetalrooster commented Oct 29, 2020 •
edited
Loading

We have taken notice of that request. Many thanks for your contribution.

@gtsiolis gtsiolis mentioned this issue Dec 14, 2020
Closed
@Michaelhobo
Copy link

+1

@gtsiolis gtsiolis mentioned this issue Mar 9, 2021
Closed
@stale
Copy link

stale bot commented Mar 17, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Mar 17, 2021
@stale stale bot closed this as completed Mar 27, 2021
@gtsiolis
Copy link
Contributor

Re-opening as it's still relevant. Cc @jldec

See also #2527 (comment) and workaround mentioned in #2058 (comment) (Cc @corneliusludmann).

Cc @mrsimonemms because #7025 (comment)

@gtsiolis gtsiolis reopened this Dec 14, 2021
@stale stale bot removed the meta: stale This issue/PR is stale and will be closed soon label Dec 14, 2021
@gtsiolis gtsiolis added component: dashboard team: webapp Issue belongs to the WebApp team meta: never-stale This issue can never become stale labels Dec 14, 2021
@loujaybee loujaybee mentioned this issue Jun 21, 2022
Open
@loujaybee
Copy link
Member

Please note some related issues that might help alleviate some pains here:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component: dashboard meta: never-stale This issue can never become stale team: webapp Issue belongs to the WebApp team type: feature request New feature or request
Projects
🍎 WebApp Team
Status: No status
Milestone
No milestone
Development

No branches or pull requests
7 participants
@ceefour @gtsiolis @svenefftinge @Michaelhobo @loujaybee @fullmetalrooster @corneliusludmann