Undefined behavior when calling GetLifecycleConfiguration

[kikaragyozov]

Describe the bug

Documentation clearly states the following for GetLifecycleConfiguration:

Prior to updating the SDK, everything was working as expected, but when we updated to the latest version, our code completely broke down, because now, the API does not throw such a special error when a NotFound status code is returned.

This is a major breaking change, is undocumented, and undefined behavior.

If you could please investigate this as it's entirely possible the same type of handling is being done to other endpoints.

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

An exception be thrown as previously so.

Current Behavior

No exception is thrown.

Reproduction Steps

Call the method when there is no lifecycle rule defined.

Possible Solution

No response

Additional Information/Context

No response

AWS .NET SDK and/or Package version used

AWSSDK.S3 - 4.0.17.2

Targeted .NET Platform

.NET 10

Operating System and version

Windows 11

[kikaragyozov]

After a more thorough investigation, the assert that failed us was that the Configuration property of the returned object was expected to be non-null. In V4 - it's null.

Unlike other null-aware properties, this property was not specified as nullable.

[peterrsongg]

@kikaragyozov strange, I just called GetLifecycleConfiguration on a bucket with no Lifecycle rule defined and the returned Configuration object wasn't null for me. We even have a custom getter defined here. But the fact that your code is now breaking suggests maybe something else is wrong? Can I ask what version did you upgrade from?

[github-actions]

This issue has not received a response in 5 days. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.

[kikaragyozov]

@kikaragyozov strange, I just called GetLifecycleConfiguration on a bucket with no Lifecycle rule defined and the returned Configuration object wasn't null for me. We even have a custom getter defined here. But the fact that your code is now breaking suggests maybe something else is wrong? Can I ask what version did you upgrade from?

The version we upgraded to is AWSSDK.S3 - 4.0.17.2

The version we upgraded from is AWSSDK.S3 - 3.7.510.4

I apologies for the late reply on this. Hopefully you're able to see this.