search

aws-cloudformation / aws-cloudformation-resource-providers-stepfunctions

The CloudFormation Resource Provider Package For AWS Step Functions
https://aws.amazon.com/step-functions/
Apache License 2.0
6 stars 4 forks source link

Cloudformation does not add `StackName` to the `State machine` name #44

Closed mskogorevrmc closed 1 year ago

mskogorevrmc commented 1 year ago

I noticed that if I don't add StateMachineName in the template, then the name State machines is generated as follows: [resource]-[uniqid] but for all other resources in the template (Roles,LogGroup and etc), StackName is added to the name: [stackname]-[resource]-[uniqid]

Is this a bug or is this how it should work? Thanks

wong-a commented 1 year ago

This is by design. CloudFormation does not prescribe a particular naming convention for physicalIds, other than that they should be unique. Do you have a use case requiring a particular naming convention?

This was discussed in a previous issue: https://github.com/aws-cloudformation/aws-cloudformation-resource-providers-stepfunctions/issues/26#issuecomment-1472949187