How to ensure consistency of Serverless business deployment updates?

Since I started working on Serverless tools, I often encounter people asking this question: How to ensure the consistency of Serverless business deployment updates?

The so-called consistency here means: we deploy the project locally through tools. At this time, someone updates the project through other channels (such as console, etc.). If I deploy the project locally again, will it be directly overwritten?

For example, when user A updates the business locally, due to some special circumstances, an online exception "x" occurs. At this time, user B updates again and fixes the content, but B does not synchronize this to A in time. A updates a new function and directly overwrites B's content. At this time, the previous exception x appears again. If A can sense that the online resources have changed when updating at this time, then this incident will not happen again.

Currently, the Alibaba Cloud Function Compute component based on Serverless Devs already supports the ability to perceive online "changes", including the following situations:

Create and deploy a resource locally that is not available online. Complete local deployment, update online, and deploy locally again. Create and deploy a resource that is already available online locally.

Experimental preparation

Create a function through s init (select Alibaba Cloud Serverless, select HTTP Function - Python3 Example):

Now let's take a look at s.yaml:

After the project is deployed online, a fc-deploy-service service and an http-trigger-function function are created in the cn-hangzhou zone.

Create and deploy a resource locally that is not available online

At this point, we confirm that there are no corresponding resources online, so we deploy them:

The deployment was completed smoothly:

Open the browser and check the custom address given to us:

At this point, we can update this function code locally:

Save the deployment:

After completion, check out the online resources:

The whole process is relatively close to the traditional basic process and does not trigger any online changes. It can be considered an ideal process.

Local deployment is complete, online updates are made, and local deployment is repeated

At this point, we make changes to the online resources. First, find the function in the console:

Modify the code and deploy it.

After the deployment is complete, let's refresh the address just now:

You can see that it has been updated. At this point, we deploy it locally:

As you can see, the system has sensed our code changes. At this time, we select yes and check the online resources after completion:

It should be noted that any changes in the service, function, or trigger of Function Compute can be detected here, regardless of configuration or code.

Create and deploy an existing online resource locally

At this point, we will conduct the final experiment. We will delete the local project and rebuild it. Then we will deploy it. Due to the reasons in the previous experiment, we already have these resources online, so this is considered to be deploying an online resource.

At this point, you can see that the system senses that this resource has not been deployed locally, but is online and already exists, so it is necessary to determine whether to overwrite it.

Summarize

When the code is updated in other scenarios, we need to be aware of it at the moment. This is actually very important and is essential to the safe release of the code. At this time, Serverless Devs can do it.

So the question is, if I already have a project and I want to integrate it into the CD process, and I don’t want interactive operations, how should I deal with it?

At this time, we provide a --use-local parameter to forcibly overwrite the online configuration. Through such instructions, non-interactive and local priority can be achieved.

The birth of every tool has a growth process, and Serverless Devs is constantly growing. We look forward to more and better features.

Original link: http://click.aliyun.com/m/1000284611/