Open ilons opened 5 days ago
Thanks @ilons for reaching out. I tried to reproduce this issue but was not able do. When running the describe_change_set
command and getting a FAILED
status, I got the StatusReason
in my response with IncludePropertyValues
was either set to True
or False
.
Could you provide code snippets to help us reproduce the issue? Also if you can share debug logs (with sensitive info redacted) by adding boto3.set_stream_logger('')
to your script, that could give us insight into the underlying issue here.
Boto3 commands like describe_change_set involve calls to upstream APIs (in this case DescribeChangeSet) so there may be some edge case issue with the CloudFormation API and/or here that we would need to escalate to that team.
Could you provide code snippets to help us reproduce the issue? Also if you can share debug logs (with sensitive info redacted) by adding
boto3.set_stream_logger('')
to your script, that could give us insight into the underlying issue here.
Thank you for the swift response, I'm afraid it would be very hard for me to provide this in the same timely fashion, as I'm leaving for vacation. However, I'll put a note to provide this as soon as I get back.
Describe the bug
When calling the
describe_change_set
function on acloudformation
client for a stack withIncludePropertyValues
set toTrue
, the response does not includeStatusReason
if the change setStatus
isFAILED
.Expected Behavior
The
StatusReason
should be included in the response both whenIncludePropertyValues
is set toTrue
.Current Behavior
The response returned does not include the
StatusReason
for a change set with aStatus
ofFAILED
(at least not when it failed due to no changes). When performing the same call withIncludePropertyValues
set toFalse
, theStatusReason
is included in the response.Reproduction Steps
Create a CloudFormation stack Call
create_change_set
using the same template Calldescribe_change_set
on the created change set withIncludePropertyValues
set toTrue
Possible Solution
No response
Additional Information/Context
This seems to be a bug in CloudFormation itself, as the AWS Console are performing two calls when viewing a change set, one with include property values set to true, and one with it set to false.
SDK version used
1.34.134
Environment details (OS name and version, etc.)
Python 3.10.12, Linux Pop!_OS 22.04 LTS