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.

Sign up for GitHub

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

Jump to bottom

Add the ability to customize lambda function upload name #49

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Add the ability to customize lambda function upload name #49

wants to merge 3 commits into from

Commits on Jun 8, 2016

  1. Add the ability to customize lambda function upload name 

    This allows lambdas uploaded to gordon to contain a chosen base function
name, combined with "AWS::Region" and "Stage" references to keep
uniqueness across stages / regions.
    @glaurungg
    glaurungg committed Jun 8, 2016
    Configuration menu
    Copy the full SHA
    c044c04 View commit details
    Browse the repository at this point in the history

Commits on Jun 9, 2016

  1. Prepend app name to Ref type lambda FunctionNames 

    Fixes a small bug where the app name was only being prepended to string
type lambda function names and not troposphere.Ref types.
    @glaurungg
    glaurungg committed Jun 9, 2016
    Configuration menu
    Copy the full SHA
    3a8d951 View commit details
    Browse the repository at this point in the history

  2. Fix minor naming consistency issue 

    Because of the timing of when troposhere.Ref objects are resolved in a
Fn::Join, the format of rule names is now consistently
"AppName-LambdaName-Stage-AWS::Region"
    @glaurungg
    glaurungg committed Jun 9, 2016
    Configuration menu
    Copy the full SHA
    e471b8e View commit details
    Browse the repository at this point in the history