JSON order matters for parsing?

@lfbrock I'm still very confused. I've modified the service to quote every parameter... It should work.

In fact when I send it to Mattermost 3.4.0 through curl, it does work! Only when I try to retrieve it through a custom command does it ignore the attachments.

Here's the better formatted json I captured as output by my microservice that I successfully saw posted in the test channel through curl to an incoming webhook:

{"attachments": 
  [
   {"color": "good", "fields": 
    [{"short": "true", "title": "Time since created", "value": "1 day 00:41:27.398337"}, 
     {"short": "true", "title": "Completed", "value": "100.00"}], 
  "pretext": "Run progress", 
  "title": "Run 1725"}, 
  {"color": "#888888", "fields": 
  [{"short": "true", "title": "Sources Processed", "value": "117602451"}, 
   {"short": "true", "title": "Total Sources", "value": "117603945"}, 
   {"short": "true", "title": "Sources per minute", "value": "79407"}, 
   {"short": "true", "title": "Estimated Completion", "value": "00:00:01.128861"}], 
  "pretext": "Detailed statistics", "title": "1725"}
], 
"response_type": "in_channel", "text": "Run status on dpac_c2"}

This is the hook.py I wrote, which I basically modified from the mattermost-jira-info. Perhaps I'm doing something wrong? It was originally intended to respond to an outgoing webhook, not a custom command integration. But it should be the same given that it's also configured as a POST, correct?

NOTE: currently the hook.py is deployed calling the formatting without the attachments, but I think the color and format brought about from the attachments would be appreciated in our use-case. So it's not a blocker, but it is definitely something I'm looking forward to resolving.