YAML creates nested objects instead of string representations

ESDomain.AdvancedOptions parsed to object.

Description

The update/deployment of an “AWS::Elasticsearch::Domain” using 1.13.x

For bug reports:

The AdvancedOptions are broken and invalid for cloudformation:

  Serverless Error ---------------------------------------
 
     An error occurred while provisioning your stack: ESDomain
     - Value of property AdvancedOptions must be an object
     with String (or simple type) properties.

The cloudFormation definition should provide the following options:

   "AdvancedOptions": {
          "rest.action.multi.allow_explicit_index": "true",
          "indices.fielddata.cache.size": ""
}

Here are the AWS::Elasticsearch::Domain defintions

resources:
  Resources:
    ESDomain:
      Type: AWS::Elasticsearch::Domain
      Properties:
        AccessPolicies: 'xxx'
        DomainName: xxxx
        ElasticsearchVersion: "5.1"
        ElasticsearchClusterConfig:
          InstanceType: t2.medium.elasticsearch
          InstanceCount: 1
        EBSOptions:
          EBSEnabled: true
          VolumeType: standard
          VolumeSize: 10
        AdvancedOptions:
          rest.action.multi.allow_explicit_index: "true"
          indices.fielddata.cache.size: ""

Here is the cloudformation-template-update-stack.json (ES.Domain AdvancedOptions part) which is invalid for cloud-formation.

        "AdvancedOptions": {
          "rest.action.multi.allow_explicit_index": "true",
          "indices.fielddata.cache.size": "",
          "rest": {
            "action": {
              "multi": {
                "allow_explicit_index": "true"
              }
            }
          },
          "indices": {
            "fielddata": {
              "cache": {
                "size": ""
              }
            }
          }
        }

Additional Data

• Serverless Framework Version: 1.13.x

[HyperBrain]

Also blocks us from upgrading to 1.13. The quoted YAML identifiers must not be parsed into objects.

[HyperBrain]

@alex20465 @pmuens There is a difference in YAML between double and single quotes. Double quotes need escaping in the quoted text, while single quotes do not.

Could you try to put the dotted keys into single quotes like this? 'rest.action.multi.allow_explicit_index': 'true'

BTW: I wonder why you also quoted the boolean value - does it have to be a string?