The yaml export doesn't use quotion marks on the right side anymore. This affects the bootstrapping (importing) of those files to end up with wrong types, which may causes bugs e.g. in the format of jcrDeliveryEndpoints returning the wrong format.

This bug actually causes more work on producing bootstrapping sample for development for an enterprise customer of us.

How to reproduce

1. Create a App via content-types that has multiple string properties and one of each type (e.g. double, long, boolean etc)
2. Add an entry in the app with some special cases
   1. Add a string that contains only numbers
   2. Add a string that is `true` or `false`
   3. Add an empty string
   4. Add a string in double format e.g. `1.2`
3. Check the jcr tree that the fields have the correct type
4. Perform an yaml export of the above entry
5. Add the entry as Bootstrap sample (maybe it alsow works with importing it directly)

Current behaviour

After importing the above node, the types are wrong since the yaml file does not contain the quotion marks anymore:

• Empty String is converted to a contentNode
• Number String is converted to a long
• Double String is converted to a double
• Boolean String is converted to a boolean

Expected behaviour

After importing the above node, the types should be the same as before:

• Empty String should be a string
• Number String should be a string
• Double String should be a string
• Boolean String should be a string

Probably reason for the bug

The reason may be that the exported yaml does not containt quotion marks on the right side anymore. Therefore the types may change during bootstrapping or exporting