Re: User defined variable "key" validation doesn't happen at cf set-env phase

Nicholas Calugar

Hi Ponraj / Padma,

Apologies for the delay. I've added a story to do environment variable
validation for our upcoming V3 api:



On Sat, Mar 12, 2016 at 5:44 AM, Padmashree B <padmashree.b(a)> wrote:

Hi Nick,

Thanks for the clarification!
But as a developer I would expect the restart/restage of the application
fails if the environment variables is invalid.
However, this is not the case always - if the var name has special
characters such as @$ etc., it fails to restart, the user can then
trouble-shoot to find the issue.
But in cases where the var name has . or -, the application
restarts/restages successfully. The app logs, however, contains ERR message
ERR /bin/bash: line 17: export: `test-dash=testing special chars': not
a valid identifier
At runtime, these invalid variables are not accessible by the application.

As a developer, I would expect, the application fails at an early stage
during restart.

Kind Regards,

Join to automatically receive all group messages.