-
Notifications
You must be signed in to change notification settings - Fork 15
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
Support tag --force in serverless-compose #167
Comments
@pdias94 PR's welcome! |
+1 for this - sometimes if a service deployment fails, subsequent deploys result in For example, consider a serverless-compose stack with two services:
It's annoying because you can't just Another example is if you were to update the function code in Service 1 and want the Cloudfront distribution to point to the new version (that's passed from Service 1 to Service 2 via serverless-compose), serverless-compose won't deploy Service 2 if its template hasn't changed. I assume this is because serverless-compose doesn't take into account changed inputs when determining whether to deploy a service. Supporting a |
+1 |
Is there an existing issue for this?
Use case description
Currently in my company I need to deploy in CI pipelines my lambda functions to multiple api gateways based on microservices by domain.
We need the deploy to ALWAYS run on the api gateway to the given stages.
Currently, serverless-compose don't have this feature.
Proposed solution (optional)
Support the
--force
tag in deploys using serverless-compose as same as the serverless default deployThe text was updated successfully, but these errors were encountered: