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

Publish Lambda function under different version tags? #88

Closed
ondrejmirtes opened this issue Nov 12, 2018 · 5 comments
Closed

Publish Lambda function under different version tags? #88

ondrejmirtes opened this issue Nov 12, 2018 · 5 comments
Labels

Comments

@ondrejmirtes
Copy link
Contributor

Hi Matthieu,
my usecase is that I'd like to have a Lambda function to run different PHPStan versions. So ideally I'd like to have the ability to invoke different lambda versions identified by a commit hash. This is possible since the invoke API has a qualifier field that does exactly this.

But how should I publish lambda function under a specific version qualified with Serverless/Bref?

Thank you.

@mnapoli
Copy link
Member

mnapoli commented Nov 12, 2018

Right, I don't know sorry. However if you depend on the lambda's version then that means you can never update your runners right?

Would it make more sense to use "stages" instead? (those can be deployed using the --stage option)

@ondrejmirtes
Copy link
Contributor Author

I don't think I have any disadvantage with this approach. I just want to run the same code under different PHPStan versions and compare the results.

@mnapoli
Copy link
Member

mnapoli commented Nov 12, 2018

Yes but let's say you want to fix an error in your runner, or update Bref?

Actually I just discovered you can use aliases (like git tags/branches). It seems you need to use a serverless plugin though: https://github.com/HyperBrain/serverless-aws-alias

@ondrejmirtes
Copy link
Contributor Author

Yeah, I'd have to update all the Lambda versions at that point.

I'm not sure whether aliases are the right solution but I will take a look 😊

@mnapoli
Copy link
Member

mnapoli commented Nov 12, 2018

👍 closing this for now.

@mnapoli mnapoli closed this as completed Nov 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants