Watson Workspace will no longer be available after February 28, 2019. Learn more.

Developers

specify an environment variable value

Comments

6 comments

  • Avatar
    JARED WALLACE

    Hi Roydan. I assume you're using Bluemix? Can you take a screenshot of this error (pixelate or block the secrets of course)

  • Avatar
    JARED WALLACE

    Nevermind, I went ahead and setup an account on bluemix and I see what you are talking about. Let me do some digging.

  • Avatar
    JARED WALLACE

  • Avatar
    JARED WALLACE

    So it looks like it's a bug in the Bluemix UI, but I spoke with the developer of that example and he says you can safely eliminate the variable and still run the app - you just won't see any debug messages.

  • Avatar
    Roydon Jeffrey

    Yea, that's exactly what I went ahead and did. I just deleted the variable and proceeded. My app is running like you said. Thanks very much for your efforts.

  • Avatar
    JARED WALLACE

    I got the following back from Bluemix support:

     

    I'm sorry to hear that you are having trouble creating an environment variable. I see that you are currently using the asterisk in your variable value. This is what is causing the issue. We are currently aware of certain symbols that will not work in the environment variable value field and are working to resolve this issue. As a temporary work around, you can issue the following command via the CF-CLI from your terminal that will allow you to create the variable name with the asterisk.

    cf set-env appname env_var_name env_var_value

     

    So then:

    1) Download the CF Terminal app: https://github.com/cloudfoundry/cli/releases

    2) run: "cf api https://api.ng.bluemix.net"

    3) run: "cf login -u [username] -o '[org name]' -s '[space name]'"

    4) run: "cf set-env [your app name] DEBUG 'workspace-*'"

    Result:


Please sign in to leave a comment.