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


Nicholas Calugar
 

No, we are trying to focus on development of the V3 API, we will only fix
major issues with the V2 API.

Thanks,

Nick

On Sun, May 15, 2016 at 8:44 PM, Padmashree B <padmashree.b(a)sap.com> wrote:

Hi Nick,

Thanks for the update!
Are there any plans of bringing it to V2 APIs as well?

Kind Regards,
Padma


Padmashree B
 

Hi Nick,

Thanks for the update!
Are there any plans of bringing it to V2 APIs as well?

Kind Regards,
Padma


Nicholas Calugar
 

Hi Ponraj / Padma,

Apologies for the delay. I've added a story to do environment variable
validation for our upcoming V3 api:
https://www.pivotaltracker.com/story/show/119590729

Thanks,

Nick

On Sat, Mar 12, 2016 at 5:44 AM, Padmashree B <padmashree.b(a)sap.com> 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,
Padma