Developer Tools provides platform-specific CLI distributions, checksums, signature information, instructions and release notes. It also exposes authorized personal-key management. The CLI version can differ from the server version. A version label does not replace integrity verification or grant additional permissions.
Before you begin
Use an authorized laboratory computer and a personal key with a defined purpose and lifetime. Keep keys out of shared arguments, screenshots, repositories and reports. Authorization remains tied to identity, tenant and permissions; the CLI does not bypass UI rules.
Procedure
- Open Developer Tools or Downloads in the account menu and choose your operating-system distribution.
- Read version, checksum, signature status and instructions. Download to an authorized local location and compare SHA-256 exactly with the published value.
- Install as instructed and run dova --version. Check which executable PATH resolves if older installations exist.
- Create a personal laboratory key where permitted and retain it through protected custody. Never include its value in documentation.
- Run dova login --url with your authorized laboratory service and enter the key through the interactive prompt. Check returned identity and tenant.
- Start with status and filtered Repository, Mapping or run lists. Compare identifiers with the UI before automating writes.
- When finished, distinguish dova logout from server-side revocation. Logout clears local authentication; revocation prevents further use of that key on other devices.
Verify the result
The checksum matches and the intended CLI reports its version. A read-only query shows the expected identity and objects. Inspect command help for the installed distribution rather than assuming every option matches another version.
Errors and recovery
A checksum mismatch blocks using the artifact until its origin is verified. For 401/403, review key validity, expiry and permissions. A timeout can leave server work running: inspect the existing attempt before retrying. Protect the local profile because it can retain authentication.
Synthetic example
On your authorized laboratory host, run dova --version and dova status --output json. Do not place a key directly in a command line or treat an example domain as a real service.
Verification scope
Use synthetic data and the role authorized for the task. Compare a visual confirmation with the saved record or relevant attempt. Retain only safe identifiers and messages for support; do not share secrets, personal information or tenant data. If an operation outcome is uncertain, check its state before repeating it.
GitOps kit per workspace
The GitOps kit 1.1.2 binds Tenant, Domain and Environment for queries, draft reservations, publications and leases. Use source.environment and source.domainId for exports; target.environment and bindings.domainId for imports. Defaults are Development and General; preserve state per target. See the Finance example and state recovery. Direct Production authoring requires governed promotion rather than the import command.