route53resolver endpoints have incorrect required argument: CreatorRequestId about botocore HOT 6 CLOSED

Boto3 (and other AWS SDKs) basically map one-to-one with the operations of a service. In order to maintain cross-SDK consistency and for scale reasons, service changes come from service teams changing the shared model file they're providing the SDKs.

from botocore.

Have noticed this isn't the only such endpoint:

AssociateFirewallRuleGroup

• API reference
• botocore/data request schema
• AWS CLI error message: "aws: error: the following arguments are required: --firewall-rule-group-id, --vpc-id, --priority, --name"

CreateFirewallDomainList

• API reference
• botocore/data request schema
• AWS CLI error message: "aws: error: the following arguments are required: --name"

CreateFirewallRuleGroup

• API reference
• botocore/data request schema
• AWS CLI error message: "aws: error: the following arguments are required: --name"

CreateFirewallRule

• API reference
• botocore/data request schema
• AWS CLI error message: "...following arguments are required: --firewall-rule-group-id, --firewall-domain-list-id, --priority, --action, --name"

The other endpoints which are documented as requiring CreatorRequestId appear to behave as documented: CreateResolverRule and CreateResolverEndpoint

from botocore.

Hi @ed-dot-miller, thanks for reaching out. The model file and documentation correctly mark this field as required, as requests cannot succeed without this parameter. The CLI and Boto3 automatically populate this field for you, but because we cannot assume all consumers of the API will have this done for them, it still needs to marked as required in the model file. AWS CLI and the SDKs generate their documentation from those model files, so the documentation still must say it is required.

from botocore.

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.

from botocore.

Hi @RyanFitzSimmonsAK, I would have thought these model files only constitute the boto3 spec, not the spec of the REST API itself? But thanks for the response!

from botocore.

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

from botocore.