aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
Glue Job Name - inconsistent naming convention
- 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::Job
### Resource name
AWS::Glue::Job
### Description
**Expected Behavior:**
Resources managed by CloudFormation follow a consistent naming pattern when a user-defined name is not specified i.e. the name of the resource would typically be `--<12-digit-hash>`.
**Current Behavior:**
When a `AWS::Glue::Job` resource is created without specifying the `Name` resource property the job is created with the name as `-<12-digit-hash>` where the maximum length of the job-name is truncated to 40 characters.
Requesting if it is possible to have a consistent naming behavior between various resource types in CloudFormation.
### Other Details
_No response_
Contributor guide
Research direction
The issue is limited to AWS::Glue::Job naming when Name is omitted; start by comparing the reported generated name with CloudFormation’s usual --<12-digit-hash> pattern and the 40-character truncation. Done means the default Glue job name follows the same convention as other CloudFormation resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 42/100