Revert SQS protocol changes

[nateprewitt]

Roll back recent SQS changes.

[codecov-commenter]

Codecov Report

Patch coverage has no change and project coverage change: -0.03 ⚠️

Comparison is base (2395012) 93.41% compared to head (6071f92) 93.38%.

❗ Current head 6071f92 differs from pull request most recent head 054004d. Consider uploading reports for the commit 054004d to get more accurate results

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #2931      +/-   ##
===========================================
- Coverage    93.41%   93.38%   -0.03%     
===========================================
  Files           63       63              
  Lines        13561    13561              
===========================================
- Hits         12668    12664       -4     
- Misses         893      897       +4     

see 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[kyleknap]

🚢

[bblommers]

Hi @nateprewitt, I was just looking into fixing this for Moto.
Will the JSON format be reintroduced at some point in the future, or is the SQS-service going to stick with XML for now?

[nateprewitt]

Hi @bblommers, this change will be rolled back out to production in the future. It's currently being reverted to help alleviate some issues with tools used in some Airflow workflows. It'll be best if anyone planning to support mocking tools move towards the JSON format seen in 1.29.127.

I'll try to proactively provide more information on timeline as we have it available.

[bblommers]

Appreciate the info @nateprewitt - having a timeline/estimate would be very useful.

Do you know if other XML-based services, like EC2 or S3, will get the same treatment?

[nateprewitt]

@bblommers I can't say anything definitively about the future. This change is currently only targeted for SQS which uses the query protocol (which is different than the XML formats used by s3/ec2).

I've passed up feedback internally to make sure we have a better rollout plan for these changes in the future though to help share information more proactively.

[bblommers]

Awesome, thanks @nateprewitt!