Default input inconsistent behaviour

[giannidallatorre]

While deploying an application is allowed to left the input field void.
If the field is void and the application provide a default value for the input the deployment will be successful.

The problem.
If you start write something in the input field and then cancel it (or maybe just selecting the field with the mouse pointer), the above behaviour will change and the void string will be provided as a value for that input, overwriting the default value.

[jadianes]

I see. I think a solution for this should be to provide default values on the manifest file so they populate the input fields. Going all the way to the terraform file will involve parsing terraform files for variable values!

[giannidallatorre]

The actual behaviour is acceptable, the portal should just check that the value is not empty, and in this case not to populate the input.

The idea of providing default values on the manifest file, so they populate the input fields, is good. I just am a little reluctant, because this means adding another layer in the resolution chain, that is already quite long.

[jadianes]

Fair point.