Mark Chappell

@felixfontein probably both together

@GomathiselviS it would be good if you could add an integration test for this.

@sjthespian Thanks for taking the time to open this issue. ec2_instance was promoted to the "amazon.aws" collection (different support policies), so I've moved the issue over there. Version 3.x of...

Looking at the latest API docs https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2.html#EC2.Client.describe_account_attributes I don't think you're correct about the whole of `aws-account-attribute-lookup` as a whole being deprecated. `max-instances` has that message and is deprecated, and...

@life5ign Thanks for taking the time to open this issue. We don't manage the templates used for generating that documentation it's managed by the Ansible Documentation Working Group. @felixfontein or...

> Thanks all! I filed the issue here because it doesn't seem to be happening for other collections--sorry for the difficulty. Yeah, we've got a lot of aliases on the...

recheck (wanted to see if the tests would timeout)

closing since this seems to be stale

The reason ec2_ami uses 'user' is because that's the terminology Amazon are using in the SDK/APIs: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ec2.html#EC2.Snapshot.modify_attribute It's not a "standard" as such, more a carry-over from Amazon calling something...

> or use existing `module.warn`? Simply using `module.warn()` makes it harder for end-users to mute the messages. `deprecation_warnings=False` only works in the when using `module.deprecate()`, making `module.warn()` for behaviour which...