-
Notifications
You must be signed in to change notification settings - Fork 41
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
Does not seem to work with the latest Serverless version (1.35.1) #25
Comments
After upgrading serverless to 1.35.1 the other day, I have noticed this too, although it also intermittently works for me. I moved the serverless package back to the following versions and noticed it as well: It finally worked again for me when I went back to 1.32.0. |
I can confirm this silently doesn't write any output files or invoke my script using serverless: 1.36.1 Does anyone have a workaround other than regression? I need later features so this is not feasible. I use this plugin to create web config files that details things like the API Gateway endpoints, things just stopped working silently after an AWS region change and clean deploy. |
Workaround is to use this fork: /~https://github.com/anttiviljami/serverless-stack-output Install via: npm install @anttiviljami/serverless-stack-output Reference from serverless.yml: plugins:
(Note quotes) |
Same issue here with |
@joshpassenger BIG Thank you! @ivictbor just replace the original with the fork above, and you should be all set. |
plugin Any reason you don't raise PR and merge the change to the main stream? |
Confirmed that this doesnt work. Also, last commit was in 2017 so this is most probably abandoned. Maybe it helps someone - I ended up avoiding this and instead using a plugin that just runs whatever custom script you feed it, on the event of finished deployment - in the script then I just use filestream to write a file with the exact desired serverless vars in the format I needed. |
Does not output the file with the latest Serverless version (1.35.1)
The text was updated successfully, but these errors were encountered: