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
Multiple developers in same service name (same serverless template) to write functions, But they don't know what function other people have,if one developer use sls deploy,he will delete the functions which other developers create. How can i use sls deploy only append my functions ?
thanks
The text was updated successfully, but these errors were encountered:
I would recommend using stage. This can then also be used to make sure you don't make changes to other infrastucture another developer may be testing with. With every resource you create add ${opt:stage} somewhere in the name. For example, I tend to name DynamoDB tables as ${self:service.name}-tableName-${opt:stage}
Then when I deploy I just add --stage to the cli command. If I want to do it just for me I use my name:
sls deploy --stage garethmcc-testing
Now I can't overwrite anyone else's functions or resources if setup correctly.
@garethmcc hi, garethmcc ,thanks very much for your help,but our lambda application ,They were developed by each individual, and maybe we have A few hundred points function,we want to put some functions into one application , but everyone deployed and developed independently,each lambda have each business name ,It's not reasonable for them to use stages,and aslo same application name is will delete others lambda function. so we now deploy each function with each application. But I don't think it's good
I think this is more of a limitation of AWS rather than the serverless framework its self due to the way cloud formation works.
What you could do, is move all the functions into a single repo with a single serverless.yml file and distribute that to all users and share the repo between all users.
I don't know if I am right, You should use CI/CD pipelines to deploy your code, implementation of Jenkins,
Travis like tools may play a good role here.
Multiple developers in same service name deploy
Description
thanks
The text was updated successfully, but these errors were encountered: