aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

[AWS::Glue::DataQualityRuleset] - [BUG] - ClientToken without apparent purpose in CloudFormation context

Open
#2,448 0 comments 1 reaction 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

AWS::Glue::DataQualityRuleset

### Resource Name

AWS::Glue::DataQualityRuleset

### Issue Description

The [resource parameters ](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-glue-dataqualityruleset.html) include ClientToken with the description `Used for idempotency and is recommended to be set to a random ID (such as a UUID) to avoid creating or starting multiple instances of the same resource.`.

I think this does not make sense in the CloudFormation context and is just a copied over remnant from the [CreateDataQualityRuleset API](https://docs.aws.amazon.com/glue/latest/webapi/API_CreateDataQualityRuleset.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

Open the contributing guide

Research direction

Start by comparing the AWS::Glue::DataQualityRuleset resource parameters with the CreateDataQualityRuleset API documentation linked in the issue. Determine whether ClientToken has a CloudFormation-specific purpose; done means its purpose is documented or the parameter is removed from the resource definition and documentation.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.