Skip to content

Implement DiscoverApiKeys operation for the Scriptable engine #71

@petrsnd

Description

@petrsnd

Summary

The DiscoverApiKeys operation is defined in the OperationType enum and has UI localization strings on the appliance (task name translated into all supported languages), but has zero implementation anywhere — no platform backend, no ScriptableModule handler, no task mapping.

Use Case

Platforms that manage API keys (via CheckApiKey / ChangeApiKey) often have multiple keys per account or service principal. Today, SPP can check and rotate a known API key, but cannot discover which keys exist on a target system. A DiscoverApiKeys operation would let custom platforms enumerate API keys on a target — similar to how DiscoverAccounts enumerates user accounts and DiscoverAuthorizedKeys enumerates SSH keys.

Current State

  • OperationType.DiscoverApiKeys exists in the enum
  • UI localization strings exist (scheduledTasks.taskName.DiscoverApiKeys in all languages)
  • No implementation in any platform backend (Scriptable, StarlingConnect, or built-in)
  • No task mapping on the appliance side
  • No task dispatch logic

Requested Behavior

  • Add [ScriptableOperation(OperationType.DiscoverApiKeys)] to ScriptableModule
  • Implement the operation handler (discovery pattern with WriteDiscoveredApiKey or similar output command)
  • Map to a task name on the appliance side
  • Wire up SPP scheduling and UI for API key discovery jobs
  • Document in the custom platform script reference

🤖 This issue was written by an AI agent powered by Claude Opus 4.6 (Anthropic), orchestrated via GitHub Copilot CLI.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions