Blocklet Server icon

Blocklet Server

Consume Blocklet Server API

Actions12

Blocklet → Get Blocklet

AI-generated

Overview

This node operation retrieves detailed information about a specific Blocklet identified by its DID (Decentralized Identifier). It allows users to fetch the core data of the Blocklet and optionally attach additional runtime information, disk information, and optional components related to the Blocklet. This is useful in scenarios where users need to monitor, manage, or analyze Blocklets within a Blocklet Server environment, such as in decentralized application management or blockchain-based service orchestration.

Use Case Examples

  1. Fetch a Blocklet's basic information by providing its DID.
  2. Retrieve a Blocklet's runtime status and disk usage by enabling the respective options.
  3. Get optional components of a Blocklet to understand its extended capabilities or plugins.

Properties

Name Meaning
Blocklet DID The unique Decentralized Identifier (DID) of the Blocklet to retrieve.
Attach Runtime Info Whether to include the runtime information of the Blocklet in the response.
Attach Disk Info Whether to include disk usage information of the Blocklet in the response.
Get Optional Components Whether to retrieve optional components associated with the Blocklet.

Output

JSON

  • did - The DID of the Blocklet.
  • name - The name of the Blocklet.
  • version - The version of the Blocklet.
  • runtimeInfo - Optional runtime information about the Blocklet, included if requested.
  • diskInfo - Optional disk usage information about the Blocklet, included if requested.
  • optionalComponents - Optional components related to the Blocklet, included if requested.

Dependencies

  • An API key credential for Blocklet Server API authentication

Troubleshooting

  • Ensure the provided Blocklet DID is correct and exists on the Blocklet Server.
  • If runtime or disk info is requested but not returned, verify the Blocklet Server supports these features and the node has sufficient permissions.
  • Common error messages include 'Not implemented blocklet action' if an unsupported operation is selected, or API request failures due to network or authentication issues.

Discussion