Especially don’t want to affect prod
# seed
d
Especially don’t want to affect prod
f
Yeah, currently, if a service has been successfully deployed to in the past, and the
serverless.yml
is not found in the subsequent deploys, the service will be marked a failed.
Deploying a dummy
serverless.yml
is probably the best workaround.