EdgeWorkers CLI The EdgeWorkers command line interface (CLI) expedites the process of registering, uploading, activating and testing EdgeWorkers functions on the Akamai Edge network.

Go to Akamai CLI for EdgeKV for information on how to manage EdgeKV databases and call the EdgeKV API from the command line.

To use this tool you need:

• Akamai CLI installed.
  • If you do not have the CLI and are using Homebrew on a Mac, run this command: brew install akamai
  • You may also download OS-specific CLI binaries or a Docker image
• Valid EdgeGrid credentials configured via Akamai Control Center (see Get Started with APIs)
• Node version 14 or higher

• If you do not have the EdgeWorkers CLI package installed, use the following Akamai CLI command to install the latest EdgeWorkers CLI package:

Usage:
akamai install edgeworkers

• If you already have the CLI installed, use the following Akamai CLI command to install the latest EdgeWorkers CLI package that includes EdgeKV functionality:

Usage:
akamai update edgeworkers

The EdgeWorkers CLI lets you set default values for the command options. There are two ways to create a config file:

1. Create a config file ~/.akamai-cli/ew-config, and store the properties as follows:

[default]
edgeworkerName=testEW
groupId=12345
versionId=1-0-2

2. Use the config command to set default properties: akamai edgeworkers config set <key> <value>

Available property names are displayed here.

EdgeWorkers CLI enables you to manage EdgeWorkers functions by calling the EdgeWorkers API.

Conventions:

• optional args []
• required args <>

Usage:
akamai edgeworkers [options] [command]

Options:

Commands:

Customer Developer can find their EdgeWorkers access level per Luna Access Control Group.

Usage: akamai edgeworkers list-groups [options] [group-identifier]

1. Output is filtered to only those Luna Access Control Groups that have at least one EdgeWorkers capability.

2. Capabilities can be: VIEW,VIEW_VERSION,EDIT,VIEW_ACTIVATION,CREATE_VERSION,ACTIVATE

List EdgeWorker ids currently registered.

Usage: akamai edgeworkers list-ids [options] [edgeworker-identifier]

Register a new EdgeWorker id to reference in Property Manager behavior.

Usage: akamai edgeworkers register [options] <group-identifier> <edgeworker-name>

1. Location response header will be provided with new EdgeWorker Id.

2. EdgeWorker id details response body (JSON) will be provided with 201 response code.

3. To disable prompts for automation purpose "resourceTierId" can be provided as input.

Allows Customer Developer to update an existing EdgeWorker Identifier's Luna ACG or Name attributes.

Usage: akamai edgeworkers update-id [options] <edgeworker-identifier> <group-identifier> <edgeworker-name>

1. API requires that both groupId and name be provided even if only changing one of these attributes.

2. EdgeWorker id details response body (JSON) will be provided with 200 response code.

3. Resource Tier ID provided should be same as the one the EdgeWorker ID already has. In order to provide a different resource tier id, please use the clone operation.

Permanently delete an existing EdgeWorker Identifier.

Usage: akamai edgeworkers delete-id [options] <edgeworker-identifier>

1. Deleting an EdgeWorker ID is only possible if it doesn't have any version currently active or being activated on the Akamai network.

2. Ensure that there are no active properties associated with an EdgeWorker before deletion.

List Version information of a given EdgeWorker Id.

Usage: akamai edgeworkers list-versions [options] <edgeworker-identifier> [version-identifier]

1. Result set is sorted by an upload sequence value that is not displayed (an internal incremented integer).

2. EdgeWorker versions are customer defined strings.

Creates a new version of a given EdgeWorker Id which includes the code bundle.

Usage: akamai edgeworkers upload [options] <edgeworker-identifier>

1. One of either --bundle or --codeDir (but not both) must be provided.

2. Code bundles paths and files must be found on the local filesystem.

3. --bundle expects a tgz file already built per EdgeWorkers specification.

4. --codeDir expects a directory path which contains both the main.js (events file) and bundle.json (manifest file).

5. --codeDir option will provide bundle.json format validation.

6. --codeDir does not pack other directories or code beyond main.js and bundle.json.

7. --codeDir will build the tarball (tgz) file if file validation succeeds.

8. Service will compare new tarball's checksum with previously uploaded tarballs for the same EdgeWorker id (ewId). If a match is found, the new version creation is disallowed.

9. versionId is customer generated and will be pulled from bundle.json.

10. Location response header will be provided with new EdgeWorker Version id.

11. EdgeWorker version details response body (JSON) will be provided with 201 response code.

Permanently delete an existing version of a given EdgeWorker Id.

Usage: akamai edgeworkers delete-version [options] <edgeworker-identifier> <version-identifier>

1. Deleting a version is only possible if it is not currently active or being activated on the Akamai network.

2. If the version is currently active, it will have to be deactivated before it can be deleted.

Download the code bundle of an EdgeWorker version.

Usage: akamai edgeworkers download [options] <edgeworker-identifier> <version-identifier>

1. If --downloadPath is not provided or is not found on local filesystem, an AkamaiCLI cache sub-directory will be used: <CLI_CACHE_PATH>/edgeworkers-cli/edgeworkers/<ewid>/

List Activation status of a given EdgeWorker Id.

Usage: akamai edgeworkers status [options] <edgeworker-identifier>

1. You may not provide both the Version and the Activation identifiers.

Activate a Version for a given EdgeWorker Id on an Akamai Network.

Usage: akamai edgeworkers activate [options] <edgeworker-identifier> <network> <version-identifier>

1. Network must be either STAGING or PRODUCTION. Capitalization will be normalized to uppercase.

2. Location response header will be provided with new EdgeWorker Activation id.

3. EdgeWorker activation details response body (JSON) will be provided with 201 response code.

Validates a code bundle version without uploading the code bundle

Usage: akamai edgeworkers validate [options] <bundlePath>

1. Code bundle path must be found on the local filesystem.

2. Code bundle expects a tgz file already built per EdgeWorkers specification.

Deactivate a Version for a given EdgeWorker Id on an Akamai Network.

Usage: akamai edgeworkers deactivate [options] <edgeworker-identifier> <network> <version-identifier>

1. Network must be either STAGING or PRODUCTION. Capitalization will be normalized to uppercase.

2. Location response header will be provided with new EdgeWorker Activation id.

3. EdgeWorker activation details response body (JSON) will be provided with 201 response code.

Generates an authentication token that can be used to get detailed EdgeWorker debug response headers. You need at least version 1.7.1 of the EdgeWorkers CLI to run this command. Use the -V, --version option to display the current version number of the EdgeWorkers CLI.

Usage: akamai edgeworkers create-auth-token [options] <hostName>

1. The --expiry value must be between 1 and 720 minutes (12 hours). The default is 8 hours.

Allows customer to clone an EdgeWorker from an existing EdgeWorker Id.

Usage: akamai edgeworkers clone <edgeworker-identifier> <resourceTierId> [options]

1. This endpoint allows user to select a different Resource Tier ID for a specific EdgeWorker id by cloning it. Cloning to the same resource tier will fail.

List of contract ids that user has access to.

Usage: akamai list-contracts

List of properties associated to a specific EdgeWorker Id.

Usage: akamai edgeworkers list-properties <edgeworker-identifier> [options]

1. Note that the returned boolean limitedAccessToProperties is true if the user doesn't have access to the top level group under the account, or if they don't have the admin role for this group.

List the various limits EdgeWorkers imposes on the number of activations, EdgeWorkers IDs, and versions you can deploy.

Usage: akamai edgeworkers list-limits [options]

List Resource Tiers that can be used to create or clone EdgeWorker IDs.

Usage: akamai list-restiers

1. User will be prompted with list of contract ids that user has access to. The selected contract id will be used to fetch resource tier.
2. To disable prompt for automation purpose, contract id can be provided as input.

Customers can get Resource Tier details for a specific EdgeWorker Id.

Usage: akamai show-restier <edgeworkerId>

List the available report types that can be generated for an EdgeWorker ID.

Usage: akamai get reports

1. The user will be given a table with reportIds and a description of each report. Use a given reportId with the get report command to get a report for a given EdgeWorker.

Get a report for a given EdgeWorker ID.

Usage: akamai get report <reportId> <edgeworker-identifier>

1. For a list of available report IDs, use the get reports command.
2. The startDate option is a required option.

Get all default properties in a section of the config file.

Usage: akamai config list

1. The config section is default by default. To use a different seciont, users should specify the akamai edgeworkers command with option --configSection <configSeciont>.
2. Same approach should apply to the following config commands.

Get one specific default value in a section of the config file.

Usage: akamai config get <key>

Allows customers set/update a specific default value in a section of the config file.

Usage: akamai config set <key> <value>

Allows customers unset a specific default value in a section of the config file.

Usage: akamai config unset <key>

Allows customers save the default values in bulk.

Usage: akamai config save [options]

1. If the context contain invalid item, the command will skip that item and continue.

For more information on EdgeWorkers, refer to the following resources:

• EdgeWorkers Developer Page
• EdgeWorkers User Guide
• EdgeWorkers API Guide

You are all set, happy coding! If you experience any issues with the EdgeWorkers CLI, raise them as a github issue. Feel free to create a pull request with the fix or suggestion.

We welcome contributions from Akamai staff, customers, or others. Before opening up a PR please double check the following:

1. Please add some test cases to accompany your PR. This verifies the functionality added or modified in the PR and proves to others that your code works :)
2. Please make sure that your code passes all pre-commit checks. Your code should build successfully, pass all unit tests, and have no linting issues.
3. All PR's should be targeting develop, not master. Merges to master will immediately release to all customers.