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

Ponraj E

Hi CF Colleagues,

I see various PaaS providers provide the UI for entering the User provided variables' key and value, but they dont seem to validate the "key" at the save ["set-env"] phase, the validation happens only at
the restage phase. This is also because CF does the same. Is there any reason that CC doesnt validate keys of user defined environment varibles at the cf set-env phase ?

Examples: set-env spring-music !@#$$%% "foobar" succeeds, but the restage fails throwing /bin/bash: line 6: export: `!@#49%%=foobar': not a valid identifier set-env spring-music "!@#$$%%" "foobar" succeeds, the restage also succeeds but the same as above is thrown as message here.

P.S: The above variables are used for only testing purposes and these would give errros at the runtime usage in the application is implicit here.


Join to automatically receive all group messages.