-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sqs create_queue does not return QueueUrl
since v1.34.90
#3169
Comments
Hi @zodiac403 thanks for reaching out. There was a recent change in 1.34.90 related to SQS:
However, the response syntax should be the same. I just tested your snippet in both 1.34.89 and 1.34.90 and confirmed that It looks like in moto version 4.2.10 is where support for the SQS change was added. |
Hi @tim-finnigan , thanks for the very quick response. I will check that out on my side. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Hi @tim-finnigan , indeed, there was moto pinned to an old version in this project. Appreciate your support here! |
I have same error, although no moto package installed. |
The same goes for me. Moto and similar are not used, but 1.34.90+ fails with this error. |
Describe the bug
Sample code to reproduce the issue:]
According to boto docs,
create_queue()
should return a dict like { 'QueueUrl': 'string' }https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/sqs/client/create_queue.html
With version
botocore==1.34.89
this is still the behavior I can observeExpected Behavior
Resolve URL with
queue_url = queue["QueueUrl"]
Current Behavior
queue_url = queue["QueueUrl"]
results in aKeyError
as the the result ofcreate_queue()
does not have an entry"QueueUrl"
.Reproduction Steps
Code sample above
Possible Solution
No response
Additional Information/Context
No response
SDK version used
Observed the issue in
1.34.90
, could not reproduce the issue in1.34.89
Environment details (OS name and version, etc.)
MacOs Sonoma 14.4
The text was updated successfully, but these errors were encountered: