Keeping deployments up-to-date

In order to provide the best experience possible and the latest profiling capability, Darwinium recommends re-building/re-deploying journeys every 2 months or when.
From time-to-time Darwinium may also issue security advisories to our customers requesting re-building of edge artifacts.

By virtue of rebuilding your node's edge functionality will be updated to the latest version. For our AWS customers this also means updates to Lambda runtimes.

How to re-build a deployment artifact

In the Darwinium workflow editor, open a terminal  and run the following commands:

git commit --allow-empty -m "Forced rebuild"
git push

The journey will be automatically built and may be deployed at your convenience.

Why doesn't Darwinium do this for me Automatically?

Your node's deployment credentials (if using deployment manager) are considered especially sensitive and cannot be unlocked or read by Darwinium's automated process. By design, we require a human with manage deployments permission on a node to manually execute deployments.

Notes on AWS Lambdas

Our internal deployment manager uses the following configuration when deploying Lambda functions. This information is also provided to Terraform users in an edge bundles workers.json manifest:

    "handler": "index.handler",
    "runtime": "nodejs18.x",
    "architectures": ["x86_64"],
    "memory_size": 128,
    "timeout": 5,
    "publish": true,