Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Application name parsing error #243

Closed
ehelbig1 opened this issue Apr 21, 2020 · 1 comment
Closed

Application name parsing error #243

ehelbig1 opened this issue Apr 21, 2020 · 1 comment

Comments

@ehelbig1
Copy link

I ran into an error, snsdev-dev already exists, when trying to create a new project. After a bit of digging it appears that root of the problem is the generation of resource names:

RoleName: !If [ShouldNotCreateEnvResources, 'boardg891ab340_sns-role', !Join ['',[ 'sns', !Select [3, !Split ['-', !Ref 'AWS::StackName']], '-', !Ref env]]]

This pattern is present in many location throughout the CloudFormation templates and dictates that there must be a convention followed when naming applications. This convention is not enforced through the CLI when initially creating the project.

A name like example-app breaks this convention and can cause issues.

Can the resource name generation algorithm be changed to support additional conventions?

If not, can restrictions on project names be added to the CLI?

@aspittel
Copy link
Contributor

aspittel commented Oct 7, 2022

Sorry for the slow response on this, if your're still seeing this issue can you post it on the amplify-cli repo? Thank you!

@aspittel aspittel closed this as completed Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants