This repo is a sample for Durable Functions which enable you to Zero downtime deployment.
When you change Orchestrator logic or the interface of Activity Functions, please execute the script.
This script enbable us to versioning your Durable code. It will do
Even if you have a running instances, your deployment won't harm your running process.
Follow the naming convention.You need to follow the Naming Convension.
Naming convention of the Durable Functions codeFunction name of Orchestrator Client, Orchestrator, Activity Function should be named as functionname_d_d_d
d is any int number (Semantic versioning).
For example,
[FunctionName("VersioningSample_1_0_5")]
public static async Task<List<string>> RunOrchestrator(
[OrchestrationTrigger] DurableOrchestrationContext context)
:
You can see the example on this repo.
cd command
node migration.js NEW_VERSION
Use semantic versioning.
Currently, the script doesn't support subdirectory. I'll fix it soon.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4