Is there an existing issue for this?
Use case description
Want to flag out that this is another approach of solving #9931
we are having a gitlab-ci process which include serverless deploy and we want to implement a fast rollback option (since the packaging process can take crucial time :) )
right now we are rollbacking to the -1 version (based on a script) which is good.. but we want to have more verbose way..
Proposed solution (optional)
sls.yml
provider:
deployment:
metadata:
commit_sha1: ${env:commit_sha1}
store it under the s3 object user-defined metadata
present sls metadata during the serverless deploy list
🎊
Is there an existing issue for this?
Use case description
Want to flag out that this is another approach of solving #9931
we are having a gitlab-ci process which include serverless deploy and we want to implement a fast rollback option (since the packaging process can take crucial time :) )
right now we are rollbacking to the -1 version (based on a script) which is good.. but we want to have more verbose way..
Proposed solution (optional)
sls.yml
store it under the s3 object user-defined metadata
present sls metadata during the
serverless deploy list🎊