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

Create a "DefaultStackName" Section

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

Description

### Name of the resource

Other

### Resource name

Template anatomy

### Description

I'd like to include a Default Stack Name in the template and allow it to use some Pseudo Parameters

For example:

``` YAML
Description: SampleStack with a default stackname

DefaultStackName:
!Sub: "MyStack-$(AWS::Account}-${AWS::Region}"

Resources:
<.....>

```

Some of the benefits would be:

1. Consistency in naming when deploying to multiple accounts and regions.
2. Improved development speed and testing of new templates by having one less thing to type.

### Other Details

Here are a couple of other people that have requested this feature:

https://stackoverflow.com/questions/51828313/is-it-possible-to-statically-specify-awsstackname-inside-a-cloudformation-temp

https://www.reddit.com/r/aws/comments/oix0wj/specify_stack_name_within_cloudformation_template/

Contributor guide

Open the contributing guide

Research direction

Start with the CloudFormation template anatomy described in the issue and review the linked requests for the expected DefaultStackName behavior. No repository files, tests, or entry points are named; done would mean defining and documenting a template section that accepts pseudo parameters and provides a default stack name.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.