Mark Chappell

@nethershaw, Thanks for taking the time to open this issue. I personally prefer to consistently return details of the resource, even when no changes are made. I've tweaked the subject...

@markuman The slightly confusing thing here is that s3_lifecycle (which manages the lifecycle configuration of s3 buckets) lives in community.aws, whereas s3_bucket (which creates the buckets) lives in amazon.aws. In...

There's two options: 1) Keep the current structure 2) *Deprecate* the current structure and use something closer to the API I would actually lean towards 2 as it feels slightly...

> Shall we support both as valid input formats? Having dealt with all sorts of cross-account fun in the past few years, I'm a fan of supporting full ARNs in...

@srees Our integration tests are actually based upon the same type of temporary credentials as are used for federated access. So this should already be functioning. The important thing to...

@danielmotaleite The problem is that SFAIK none of the maintainers are using AWS's SSO offering, so we can't even be sure why it's not working, or test any fixes. I,...

@alinabuzachis It's documented in https://github.com/ansible-collections/amazon.aws#aws-sdk-version-compatibility since the 2.0 release (where we required `boto3 >= 1.15.0`) That said, it looks like I didn't update the inventory plugin docs to require a...

As a bare minimum solution #819 I agree that we should also emit a warning where the minimum requirements aren't met so I'm going to leave this open for now.

+1 to consistent behaviour ( see also consistent module naming :) ) But there's two sides to the default behaviour coin: As a 'user' I often want purge to default...

This feels a lot like the instability we were seeing in https://github.com/ansible-collections/amazon.aws/pull/180 where filtered searches were (are) randomly returning empty results - I switched over to running the describe based...