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

Configuring of named variable with underscore in name doesn't work if it was set using environment variables #2454

Closed
garagatyi opened this issue Sep 15, 2016 · 5 comments · Fixed by #2664
Labels
kind/bug Outline of a bug - must adhere to the bug report template.

Comments

@garagatyi
Copy link

It is possible to configure Che using environment variables instead of property file.
Supposed way of doing that is:
env variable CHE_SOME_PROPERTY is converted into some.property.

But it is not possible to configure property if it contains underscore, e.g. some.variable_with_underscore.

Che version: 5.0.0-M2
OS and version: Linux (behavior will be the same for any OS)
Che install: Docker container

Additional information:

  • Problem started happening recently, didn't happen in an older version of Che: [Yes - there was no env variable injection before]
  • Problem can be reliably reproduced, doesn't happen randomly: [Yes]
@garagatyi garagatyi added the kind/bug Outline of a bug - must adhere to the bug report template. label Sep 15, 2016
@TylerJewell
Copy link

Cannot reproduce.

Use double underscore to create underscore. See the docs.

@garagatyi
Copy link
Author

@TylerJewell
Copy link

I still cannot reproduce this. If you use the CLI, then the underscores are converted.

@garagatyi
Copy link
Author

Can you provide steps to reproduce that it is working?

@TylerJewell
Copy link

  1. Get CLI
  2. export CHE_PROPERTY_machine_ws__agent_max__start__time__ms=1000
  3. che start

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants