Skip to content
This repository has been archived by the owner on Jul 2, 2020. It is now read-only.

Unable to assign config values that expect a List #2

Closed
bravetarget opened this issue Sep 14, 2018 · 2 comments
Closed

Unable to assign config values that expect a List #2

bravetarget opened this issue Sep 14, 2018 · 2 comments
Labels
bug Something isn't working

Comments

@bravetarget
Copy link

bravetarget commented Sep 14, 2018

Describe the bug
Defining a node configuration list/array value from the environment variables fails on launch

To Reproduce
Steps to reproduce the behavior:

  1. Define WAVES__FEATURES__SUPPORTED to be [1,2] in the environment variables
  2. Run container...
  3. See error

Expected behavior
waves.features.supported should have an array value of [1,2] in local.conf

Error Log

Exception in thread "main" com.typesafe.config.ConfigException$WrongType: /waves/configs/local.conf: 12: waves.features.supported has type STRING rather than LIST

Additional context
This is non-critical, since most of the configuration items that actually need redefining are handled with strings.

@KardanovIR
Copy link
Contributor

@bravetarget thank you for your report! This issue should be fixed with 7a647b7. Can you check it again, please?

@KardanovIR KardanovIR added the bug Something isn't working label Sep 24, 2018
@bravetarget
Copy link
Author

@KardanovIR cool! tested arrays in env injected config with 7a647b7 and that fixes it. 🎉

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants