You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for this plugin. Found it really useful with our setup to eliminate the use of function layers for common code - made it much easier to manage.
One thing I've found though, is that if you use sls package to create a package artifact of your microservice, the common symlink remains in your microservice folder.
I have worked around this via .gitignore, but it would be preferable if the plugin deleted the symlink itself after a successful package.
It seems a deploy --package <packagedir> afterwards cleans it up. I guess there is a post-package event this plugin could hook into to do the cleanup there?
Thanks,
The text was updated successfully, but these errors were encountered:
Hey there,
First of all, thanks for this plugin. Found it really useful with our setup to eliminate the use of function layers for common code - made it much easier to manage.
One thing I've found though, is that if you use
sls package
to create a package artifact of your microservice, the common symlink remains in your microservice folder.I have worked around this via .gitignore, but it would be preferable if the plugin deleted the symlink itself after a successful
package
.It seems a
deploy --package <packagedir>
afterwards cleans it up. I guess there is apost-package
event this plugin could hook into to do the cleanup there?Thanks,
The text was updated successfully, but these errors were encountered: