Developer Tools, Dova CLI and API keys

Purpose and prerequisites

Developer Tools provides the published Dova CLI catalog, platform guidance and API key tools. It shares its presentation with the Dova workspace. Opening this view or downloading a distribution does not grant access to a tenant or authorize an administrative command.

Choose the operating system of the destination machine, which may differ from the computer running your browser. Before using a downloaded tool, identify the intended laboratory workspace, the permitted operation and the credential scope required for it. Keep operational credentials outside repositories, screenshots and documentation.

Download a published distribution

1. Open Developer Tools and allow its release catalog to load.
2. Inspect the available platform entries and select the destination platform.
3. Confirm that the main download and the Quick start guidance correspond to that selected distribution.
4. Read the release information, availability, checksum and signing information exposed for the artifact.
5. Download through the published link and verify the file against the checksum for that exact artifact.
6. Follow the distribution's current Quick start steps in an authorized environment.

Availability, integrity and signing are different properties. A successful download proves neither that the file's integrity matches nor that it is signed. Describe each property according to the published metadata, and do not present an unsigned artifact as signed.

Configure permitted access

Use the supported API key flow only when your role permits it. Check the intended tenant and the available scope before creating or selecting a key. If a one-time credential is displayed, transfer it to approved secure storage without including it in shared notes or screen captures.

Copy commands from the current distribution's Quick start or its linked CLI reference. This guide intentionally does not invent subcommands, package names or flags. Document the version and required configuration for an automation, but substitute descriptive placeholders for credential values.

Acceptance exercise

In a synthetic catalog, select a Linux entry and confirm that its download, metadata and instructions agree. Switch to a Windows entry and repeat. This checks navigation and catalog consistency without installing a binary or creating a real key.

For a functional laboratory exercise, download the verified distribution and perform one explicitly permitted read operation against a synthetic resource. Record three separate outcomes: the distribution was available, its integrity matched, and the authenticated operation was authorized. Passing one outcome does not establish the others.

Errors and recovery

If no distribution is available, inspect the release catalog's message rather than guessing a URL or filename. If the checksum differs, stop using that download and obtain the correct artifact through the supported process.

For an authentication or authorization error, inspect the selected workspace, credential validity and allowed scope. Creating a stronger credential is not the first diagnostic step. Revoke or retire keys through their supported lifecycle when they are no longer needed.

Keep commands complete and copyable in downloaded documentation. Long platform tables can scroll within their own viewport. Continue with Worker installation for execution capacity and Preferences for the account and appearance controls.