-
Notifications
You must be signed in to change notification settings - Fork 68
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
Build fails: Export 'projectName-stageName-ServerlessAliasReference' does not exist #200
Comments
what is the command you run? |
@Enase : |
@Enase : Update. I ran with SLS_DEBUG on and set the level to verbose.... so here is the updated error report
|
Unfortunately I cannot help with it. |
This is an inspiration from the fix that @Enase provided long back and not merged. Tested in my local setup and works. Fixes issue serverless-heaven#186 and serverless-heaven#200
This is an inspiration from the fix that @Enase provided long back and not merged. Tested in my local setup and works. Fixes issue serverless-heaven#186 and serverless-heaven#200
@Enase: Created a PR for this #201 by looking at your serverless-aws-alias-fixed and it works. I am able to create alias successfully. I don't know why your PR is pending in such long time and it is little out of date in terms of dependencies. So hopefully this can get merged quickly so that we can drop our patch works |
@Abhijith-Nagaraja repository owner doesn't replay more then a year. I've created PS: I don't think that it's a good choice to use this plugin if you start a new project. Consider to use stages without aliases. |
@Enase Awesome, checking that out now. 👍👍👍 |
remove - serverless-aws-alias plugin and dont install that plugin. It looks like the newer versions of serverless don't require you to use that to define stages. |
Those are still struggling to get this working in 2021: I found alternative solution I used this plugin: https://github.com/davidgf/serverless-plugin-canary-deployments and use this in your yml file
|
I'm also encountering this issue. |
This works but it will throw log group alias already exist error when deploying to existing stage with same alias. Like if you have deployed it on all the following stages: dev, stg, prd and you are again deploying a change on dev. |
I am just getting started with serverless-aws-alias. But as soon as I include this plugin my build fails
Version: 1.8.0
Command:
sls deploy
Error Details
Serverless.yaml
This may be related to this issue: #181 and #186
I also applied the fix provided by @Enase in here #186 (comment) but that also did not help.
One of issue tagged here mention here about roles, and also fix provided by @Enase is also for roles. But I am not mentioning role at function level or at provider level. Is that mandatory?
The text was updated successfully, but these errors were encountered: