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
I have searched existing issues, it hasn't been reported yet
Use case description
There's a serverless package command -- I'd like to avoid needing to re-package in our CI/CD.
Proposed solution (optional)
For me, I wouldn't need no more, but for a more generic solution being able to specify the package name in the serverless-compose.yml file might be a good way.
The text was updated successfully, but these errors were encountered:
That would be great! We have a repo that contains multiple Lambda Layers. The CICD pipeline has a step that builds the desired layer, then other manual steps are used to publish to different accounts.
Without --package <path> in Serverless Compose, we'd have to rebuild each layer.
Is there an existing issue for this?
Use case description
There's a serverless package command -- I'd like to avoid needing to re-package in our CI/CD.
Proposed solution (optional)
For me, I wouldn't need no more, but for a more generic solution being able to specify the package name in the serverless-compose.yml file might be a good way.
The text was updated successfully, but these errors were encountered: