Skip to content
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.

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

Support for arbitrary strings as environment variable values #541

Closed
michaelmcneela opened this issue Aug 20, 2017 · 1 comment
Closed
Assignees

Comments

@michaelmcneela
Copy link

At the moment, evar values with newline characters seem to be rejected by the nanobox CLI, and the Dashboard replaces newlines with whitespace (flattening multi-line text to one long line)

Please can evar values be made to support arbitrary strings?– an example use of non-single-line evars being PEM-encoded encryption certificates

Thanks!

@glinton
Copy link
Contributor

glinton commented Aug 20, 2017

Currently, a workaround for this would be to load the evar from a file (new functionality), you can read more about the supported file formats here. Other than the ways we discussed on slack, i'm not sure it can be supported via the add command.

Working methods (iirc):

nanobox evar add local KEY1="-----BEGIN RSA PRIVATE KEY-----\nM\nW\nA\na\n5\nZ\nA\n5\nJ\nU\nC\na\nr\nR\nD\nS\nY\nb\n0\nK\n4\nM\nM\n1\nD\n-----END RSA PRIVATE KEY-----"

nanobox evar add local KEY2="-----BEGIN RSA PRIVATE KEY-----
M
W
A
a
5
Z
A
5
J
U
C
a
r
R
D
S
Y
b
0
K
4
M
M
1
D
-----END RSA PRIVATE KEY-----
"

glinton added a commit that referenced this issue Aug 22, 2017
Don't allow keyless evars. Resolves #544
Discontinue lodaing file contents as value on `evar add`. Resolves #545
Support for arbitrary strings as environment variable values. Resolves #541
  - We no longer split on commas, thus supporting all (bash/etc.. valid) values
@glinton glinton self-assigned this Aug 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants