CODEWITHSUNDEEP
serverless-framework
tschumann
tschumann

Reputation: 3246

Using variables in Serverless resource name

In my serverless.yml I have:

  public-function:
    handler: function.Handler

I want to parametrise the public-function line but I'm not sure how to do this. I know I can add a name: attribute to the function and use the ${} syntax documented at https://www.serverless.com/framework/docs/providers/aws/guide/variables/ but this only half solves my problem as public-function is used by Serverless as a basis for the names of other resources which I also want to have parametrised names.

Is there some way of using variables in the resource name?

Upvotes: 1

Views: 1546

Answers (1)

noetix
noetix

Reputation: 4923

The declared function key (i.e. public-function) is only a reference in the stack. There is no reason to change it at build time as the name is arbitrary.

If you want to customise the details of the deployed function, change its configuration.

For example, change the name of the function to something else using environment variables:

functions:
    main:
        handler: function.Handler
        name: ${self:provider.stage}-${env:FUNCTION_NAME}

If you are exporting the resource to another stack, you can define the export name like so:

resources:
    Outputs:
        MainFunction:
            Value:
                Fn::GetAtt: [MainLambdaFunction, Arn]
            Export:
                Name: ${self:provider.stage}-${env:CUSTOM_EXPORT_NAME}

The stage scoping to both of these examples is recommended but not required; you can name your functions, resources, and outputs anything you want.

Upvotes: 1

Related Questions