TomerShor

@dberardo-com Function versioning is not supported in Nuclio. The attribute indeed exists, but it was deprecated a while back.

@dberardo-com redeploying using PATCH released in https://github.com/nuclio/nuclio/releases/tag/1.11.17

You are doing a PUT request instead of PATCH, so the dashboard expects a full function config in the body. See https://github.com/nuclio/nuclio/blob/development/cmd/dashboard/README.md#patching-a-function

I have followed your steps and I could not reproduce. Changing the source code and PATCHing the function resulted in a rebuild with the new code. A build is required...

@dberardo-com like @liranbg mentioned in [his comment above](https://github.com/nuclio/nuclio/issues/2685#issuecomment-1507442328), you can change the CRD's `status.state` so that the controller will recreate the function resources.

@dberardo-com Like we previously discussed, changing the function spec under the hood is not recommended and can cause errors. Adding / changing triggers is done during function deployment and goes...

@dberardo-com A single trigger can also have multiple workers. In such case, each worker will have its own context, and each will receive its own termination signal.

Hey @Nokalm , Currently Nuclio doesn't support setting a custom mount type. By default, when the `type` option is not given in the `--mount`, it is using the `bind` type....

@rokatyy As discussed offline, move to draft for now until we find the best place for this doc.

Closing as it is available now as a function template.