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

[AWS::SecretsManager::SecretTargetAttachment] - [Coverage] - Target Attachment missing support for Redshift Serverless Namespace

Open
#2,082 1 comment 0 reactions 0 assignees View on GitHub
Coverage
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

AWS::SecretsManager::SecretTargetAttachment

### Resource name

_No response_

### Description

Currently, there is support the following resources:
- AWS::RDS::DBInstance
- AWS::RDS::DBCluster
- AWS::Redshift::Cluster
- AWS::DocDB::DBInstance
- AWS::DocDB::DBCluster

However, there is no support for the Redshift Namespace type (AWS::RedshiftServerless::Namespace). This is creating issues as we cannot properly make use of CloudFormation. We could make use of the secrets manager resources directly, but it would be better to have this functionality in place.

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing coverage for AWS::SecretsManager::SecretTargetAttachment and its listed RDS, Redshift, and DocDB target resources. Compare that behavior with AWS::RedshiftServerless::Namespace and identify the project entry point and validation coverage; done means the namespace target is supported for CloudFormation use. No files or tests are named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.