Deployment Confirmation

After the relevant details from the CDN have been copied into Darwinium Portal, the final part of installation involves confirmation that Darwinium logic is run; that the relevant serverless compute process is triggered and events are profiled on URL triggers within the CDN.

See journeys for full journey authoring details. The below covers the minimum needed to check installation.

Requirements to Deploy

Perform a pull of latest repository
A Journey is in repository and referenced to be built
There is a Step within Journey that is expected to trigger
Darwinium deployment target is assigned
Latest repository is commited (and therefore built)

1. Perform a pull of latest repository

Either within Source Control

Or Terminal command

git pull

2. A Journey is in repository and referenced to be built

A journeys.yaml file in root of your repository
And references a valid .journey.yaml file, also in the root (here, example.journey.yaml)

3. There is a Step within Journey that is expected to trigger

Within the journey file, make sure there is a Step that you expect to trigger.

Host: same as what you put in the Node configuration
Method, URL and URL Match Type correspond to an expected request.

It is suggested a request with lower expected volume is chosen for this confirmation Step.

4. Darwinium deployment target is assigned

In Darwinium Portal >Workflows Tab > Darwinium Deployment Targets (bottom of far right hand side)

Make sure your deployment (Cloudflare, CloudFront, Akamai) is toggled and the domain served filled in.

Press Save

This makes sure to update journeys.yaml with the target, and will now look something like:

journeys:
  - example.journey.yaml
targets:
  - name: cloudflare
    enabled: false
    valid_host_list: []
  - name: cloudfront
    enabled: true
    valid_host_list:
      - example.com

5. Latest repository is commited (and therefore built)

If you have made those changes, make sure they are commited to the repository.

Commits initiate a Build (but NOT a deploy) of the repository, which validates correctness of the configuration.

Having changes within Source Control indicates your repository contains changes not reflected in main.

Alternatively, you can run this command in terminal to check:

git status

Deploy

Important

Hitting deploy will initiate a change to the LIVE behaviour of the Darwinium serverless compute functions in your CDN
It is suggested that only admins confirm deployments, after reviews of what changes were made

When all the above are confirmed, the repository can be deployed.

'Deployment' refers to the process of packaging up the Darwinium logic commited in this version of your repository and pushing those changes back to the CDN serverless compute functions.

Go to Admin > Nodes > Cloud icon (under Actions, on node you want to deploy)
This opens up the Manage Deployments screen

Here you can:

See all previous commits to main on the repository. You should be able to see your earlier commit.
Build statuses and logs of all commits
Which commit reflects the most recent Deployment Succeeded

Important Reminder

The below action makes changes to LIVE serverless compute functions within the CDN on the host referenced by this node

Click the Deploy button (under Action) of the commit that you wish to make live.

Documentation Index