aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
[AWS::EFS::AccessPoint] - [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::EFS::AccessPoint
### Resource Name
AWS::EFS::AccessPoint
### Issue Description
The [resource parameters ](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-efs-accesspoint.html)include ClientToken with the description `The opaque string specified in the request to ensure idempotent creation.`
I think this does not make sense in the CloudFormation context and is just a copied over remnant from the [CreateAccessPoint API](https://docs.aws.amazon.com/efs/latest/ug/API_CreateAccessPoint.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
Read the AWS::EFS::AccessPoint resource parameter documentation and the linked CreateAccessPoint API documentation, focusing on ClientToken. Determine whether CloudFormation uses this parameter for a distinct purpose; done means either documenting that purpose or removing ClientToken from the resource parameters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100