ec2 create-tags doesn't allow tags via the "file" prefix

[rfein-hearst]

Since ec2 create-tags allows for tags to be supplied as JSON, I'd expect that I'd be able to supply that JSON via the "file" or "http" conventions - but it looks like the JSON has to actually supplied in-line on the command line. Not sure if this this behavior is expected or not - my assumption was that anywhere that JSON was used it could be as a file, but that may be incorrect.

aws ec2 create-tags  --tags file://tags.json  --resources i-12345678
Error parsing parameter --tags, should be: Key value pairs, with multiple values separated by a space.  
--tags Key=string,Value=string

[jamesls]

This should work. What's the contents of your json file? It should look similar to the reference docs/man page:

JSON Syntax:

[
  {
    "Key": "string",
    "Value": "string"
  }
  ...
]

[rfein-hearst]

Did some more digging - it was failing because the JSON file had a leading space on the first line. I don't believe leading whitespace should matter as the JSON is syntactically valid and passes jsonlint just fine, but sorry about the misleading initial issue.

[rfein-hearst]

Problematic JSON:

 [
    {
        "Key": "test", 
        "Value": "test"
    }
]

[jamesls]

I agree, the spacing should not matter. Looking into this.