aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
[AWS::Connect::TaskTemplate] - [BUG] - ClientToken without apparent purpose in CloudFormation context
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::Connect::TaskTemplate
### Resource Name
AWS::Connect::TaskTemplate
### Issue Description
The [resource parameters ](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-connect-tasktemplate.html)include ClientToken with the description `A unique, case-sensitive identifier that you provide to ensure the idempotency of the request.`
I think this does not make sense in the CloudFormation context and is just a copied over remnant from the [CreateTaskTemplate API](https://docs.aws.amazon.com/connect/latest/APIReference/API_CreateTaskTemplate.html). For the API it makes sense to be idempotent, but not for the deployment model of Cloudformation.
If it serves no purpose, it should be removed.
### Expected Behavior
ClientToken having a purpose or not be a parameter.
### Observed Behavior
ClientToken being a parameter without apparent purpose.
### Test Cases
documented resource parameters
### Other Details
_No response_
Contributor guide
Research direction
Start with the AWS::Connect::TaskTemplate resource parameter documentation and the linked CreateTaskTemplate API reference; compare whether ClientToken has a CloudFormation-specific purpose. Done means confirming its purpose or removing or correcting the documented parameter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100