{"action":"created","issue":{"url":"https://api.github.com/repos/aws/aws-cli/issues/1615","labels_url":"https://api.github.com/repos/aws/aws-cli/issues/1615/labels{/name}","comments_url":"https://api.github.com/repos/aws/aws-cli/issues/1615/comments","events_url":"https://api.github.com/repos/aws/aws-cli/issues/1615/events","html_url":"https://github.com/aws/aws-cli/issues/1615","id":114885408,"number":1615,"title":"Elasticsearch Service `--advanced-options` Parsing Broken","user":{"login":"bsandrow","id":72231,"avatar_url":"https://avatars.githubusercontent.com/u/72231?v=3","gravatar_id":"","url":"https://api.github.com/users/bsandrow","html_url":"https://github.com/bsandrow","followers_url":"https://api.github.com/users/bsandrow/followers","following_url":"https://api.github.com/users/bsandrow/following{/other_user}","gists_url":"https://api.github.com/users/bsandrow/gists{/gist_id}","starred_url":"https://api.github.com/users/bsandrow/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bsandrow/subscriptions","organizations_url":"https://api.github.com/users/bsandrow/orgs","repos_url":"https://api.github.com/users/bsandrow/repos","events_url":"https://api.github.com/users/bsandrow/events{/privacy}","received_events_url":"https://api.github.com/users/bsandrow/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-11-03T18:58:21Z","updated_at":"2015-11-04T01:08:36Z","closed_at":null,"body":"Per the documentation, I should be able to run this:\r\n\r\n```console\r\n$ aws es update-elasticsearch-domain-config --domain-name mylogs --region us-east-1 --advanced-options indices.fielddata.cache.size=35\r\n```\r\nWhat I get is this:\r\n\r\n```console\r\n$ aws es update-elasticsearch-domain-config --domain-name mylogs --region us-east-1 --advanced-options indices.fielddata.cache.size=35\r\nError parsing parameter '--advanced-options': Expected: '=', received: '.' for input:\r\nindices.fielddata.cache.size=35\r\n```\r\n\r\nRight now, setting Advanced Options via the CLI only works if you use the `--cli-input-json` option (e.g.):\r\n\r\n```console\r\n$ aws es update-elasticsearch-domain-config --domain-name mylogs --region us-east-1 --cli-input-json '{\"AdvancedOptions\": {\"indices.fielddata.cache.size\": \"35\"}}'\r\n```\r\n\r\nAlso, the documentation says that I should be pass `--advanced-options` like so:\r\n\r\n```\r\n--advanced-options indices.fielddata.cache.size=35 rest.action.multi.allow_explicit=false\r\n```\r\n\r\nBut adding the second option (separated by a space) results in this error:\r\n\r\n```\r\nUnknown options: rest.action.multi.allow_explicit=false\r\n```\r\n\r\n(Running Version: `aws-cli/1.8.12 Python/2.7.10 Darwin/15.0.0`)"},"comment":{"url":"https://api.github.com/repos/aws/aws-cli/issues/comments/153539008","html_url":"https://github.com/aws/aws-cli/issues/1615#issuecomment-153539008","issue_url":"https://api.github.com/repos/aws/aws-cli/issues/1615","id":153539008,"user":{"login":"kyleknap","id":4605355,"avatar_url":"https://avatars.githubusercontent.com/u/4605355?v=3","gravatar_id":"","url":"https://api.github.com/users/kyleknap","html_url":"https://github.com/kyleknap","followers_url":"https://api.github.com/users/kyleknap/followers","following_url":"https://api.github.com/users/kyleknap/following{/other_user}","gists_url":"https://api.github.com/users/kyleknap/gists{/gist_id}","starred_url":"https://api.github.com/users/kyleknap/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kyleknap/subscriptions","organizations_url":"https://api.github.com/users/kyleknap/orgs","repos_url":"https://api.github.com/users/kyleknap/repos","events_url":"https://api.github.com/users/kyleknap/events{/privacy}","received_events_url":"https://api.github.com/users/kyleknap/received_events","type":"User","site_admin":false},"created_at":"2015-11-04T01:08:36Z","updated_at":"2015-11-04T01:08:36Z","body":"Yeah looks like a bug in our shorthand syntax parsing. We recently redid it and at one point we considered making ``.`` meaningful way for expressing nested structures and members, but in the end, we decided against it."}}