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
{{ message }}
This repository has been archived by the owner on Jun 15, 2024. It is now read-only.
I'm implementing a CI on top of my app and one of the steps I want to run is sls package just to make sure all the configurations are there and the CD part will be able to run everything correctly.
My problem is that as soon as I run sls package the plugin will try to upload a new version of the layer and I don't want that extra step taking build time.
Is it possible to have a flag or bind the upload to the deploy command to force-prevent the upload of the layer and the update of the state in AWS?
That way I can have the plugin installing and doing everything it would normally do, except uploading to AWS and updating the remote state. Keep everything locally just to verify everything will be ok once we try to deploy.
The text was updated successfully, but these errors were encountered:
facing the same problem.
I am doing test to check for upgrading my databases so I need package to get access.
But it check the layers and update it if new lib or updates.
but when come the deployment, it is not deployed because the file in the s3 are up to date
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm implementing a CI on top of my app and one of the steps I want to run is
sls package
just to make sure all the configurations are there and the CD part will be able to run everything correctly.My problem is that as soon as I run
sls package
the plugin will try to upload a new version of the layer and I don't want that extra step taking build time.Is it possible to have a flag or bind the upload to the deploy command to force-prevent the upload of the layer and the update of the state in AWS?
That way I can have the plugin installing and doing everything it would normally do, except uploading to AWS and updating the remote state. Keep everything locally just to verify everything will be ok once we try to deploy.
The text was updated successfully, but these errors were encountered: