We have several developers working on our project. Would they also be required to have a serverless account and log in?
Yes. Every where you run āsls ā¦ā has to have āsls loginā done or an environment set. You can have unlimited users, even in the free tier as I understand it.
Our problem is you canāt migrate a single project/client from v3 to v4, itās all or nothing : Serverless 3 & 4 together
At some point Serverless are going to update their Chocolatey package from v3 to v4 and break everything.
What if I write this in terminal is it can deploy in v4 ?
export SERVERLESS_ACCESS_KEY="my_acess_key
Yes, that should work 
Every where you run āsls ā¦ā has to have āsls loginā done or an environment set.
Iām trying this framework for about 2 weeks. We had tried AWS SAM but this is a much simplier tool. Anyways, when I first read the pricing from the official webpage I felt like I had to pay to use it. Donāt ask me why, I believe the way youāre communicating it is confuse for some people. Aside for that, do I have to pay to use the CI/CD coming from serverless?
The features of Serverless Dashbaord such as CI/CD are paid for tools and you would need to purchase additional credits beyond the 2 free credits provided.
However, if all you want to do is use Serverless Framework CLI and are under the $2 million annual revenue threshold, there is no requirement to pay for your use of Serverless Framework and can use it as mucha s you need to
What should I do if I want to keep using serverless v3? Now it seems we are blocked by deploying our apps because even we are using v3 it is asking us to update to v4 and such. This is extremly annoying. If I have to migrate our process, why not migrate to SAM or CDK?
The process to switch to v4 is similar to what you would have had to do to switch to v3 from v2. Switching to SAM or CDK is far harder. You donāt need to āmigrate your processā. And V3 still works, nothing is blocking you from using it.
Besides that we donāt intend to depend on people purchasing licenses just because its hard to switch, but also because Serverless Framework is the best way to develop serverless applications. Its why we have no spent a huge amount of time and effort adding a ton of new features since v4 was launched, optmizing to improve the framework. Serverless Framework has not seen the kind of improvement to it that we are currently doing because now we are able to do so.
I had good experience using serverless before. Canāt understand why is so hard to separate login/dashboard/monitoring things from the framework. I donāt know a good example of paid framework that prospered after some time, especially if this changed over time.
The monitoring capabilities of Serverless Dashboard are entirely optional and require a significant process to onboard to.
Hi Suddenly I cannot deploy either and we needed to do a clean wipe on all our laptops to clear out a overly complicated authentication process. I do not want logging, AWS has ample dashboards on tracking. I want a simple way to ship microservices, and suddenly deploying an update has taken 3 days. But even worse it made my blood boil, why do you need to put your self in between me and AWS, it is meant a support package not a gatekeeper.
My main problem seems to be that your provider/ login key / license key was all tripping over each other and being written left and right, while storing old AWS credentials.
