Open aszs opened 2 years ago
In my implementation, I encode "complex" values (i.e. maps, lists, and complex data with sub-properties) using JSON, but I pass "primitive" values un-encoded. Perhaps we should specify that all values should always be JSON-encoded.
Passing an input of a data type to an operation is allowed by the TOSCA language. But the spec does not clearly define how this input is accessible from an operation implementation, for instance, how a bash script accesses to an environment variable containing the structured data input. Is it the issue?