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

Issue 95 lambda alias version #96

Merged
merged 2 commits into from
Jan 3, 2017

Conversation

anelson
Copy link
Contributor

@anelson anelson commented Jun 6, 2016

This PR resolves #95 by adding support for Version and Alias resources.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.6%) to 49.877% when pulling 80a0288 on anelson:issue_95_lambda_alias_version into 989b5c5 on MonsantoCo:master.

@anelson
Copy link
Contributor Author

anelson commented Jun 13, 2016

@tj-corrigan any objection to accepting this PR?

case class `AWS::Lambda::Alias`(name: String,
AliasName: Token[String],
FunctionName: Token[ResourceRef[`AWS::Lambda::Function`]],
FunctionVersion: Token[String],
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if this should be a ResourceRef[AWS::Lambda::Version]. If we ever needed to pass it in as a parameter we could make a special type for that as well (see something like #84).

@tjcorr
Copy link
Collaborator

tjcorr commented Jan 3, 2017

I'm going to go ahead and merge this one to clean things up. I'll make the change to FunctionVersion I suggested up above in a separate commit before I release.

@tjcorr tjcorr merged commit 0814f94 into Bayer-Group:master Jan 3, 2017
tjcorr pushed a commit that referenced this pull request Jan 3, 2017
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

Successfully merging this pull request may close these issues.

Missing support for Lambda Alias and Version resources
3 participants