Skip to content

Validate Elastic CLI extension publication after merge #342

Description

@VimCommando

Summary

After the Elastic CLI extension support merges, validate the remote GitHub extension installation path for elastic/esdiag.

Background

The register-elastic-cli-extension OpenSpec change validates local extension registration and elastic diag --help, but remote GitHub extension installation cannot be confirmed until the branch is merged and available from the public repository.

Scope

  • Confirm the repository is discoverable by the experimental Elastic CLI extension search flow, including any required GitHub repository topics such as elastic-extension.
  • Verify elastic extension install from the public GitHub repository registers the extension as diag.
  • Verify elastic diag --help reaches the esdiag command surface and includes Elastic CLI-specific help guidance.
  • Document any required publication metadata, release packaging, or installer constraints discovered during validation.

Notes

Phase one expects esdiag to already be installed on PATH; precompiled binary bundling or download behavior can be handled separately.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions