Allow passing more than one context to an extension

Open
#576 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
elasticsearch, typescript
Domain
cli

Research direction

Start by tracing how an extension process currently receives environment variables for the current context. Explore secure and ergonomic ways to pass multiple contexts, using the Elasticsearch-to-Elasticsearch piping use case as the acceptance scenario. Done means the approach is defined clearly enough to implement and its security implications are addressed.

Written by the indexing model from the issue text.

Description

Currently, an extension process is invoked with environment variables containing credentials and configurations for the current context. @VimCommando highlighed a use case where passing multiple contexts to an extension would be valuable: piping data from one Elasticsearch cluster to another.

Some discovery and experimentation is still needed to identify the most secure and ergonomic way to implement this feature.

Dominant language
TypeScript
Stars
43
Forks
24
Avg merge
1d 6h
Merged PRs (30d)
59

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elastic/cli

All issues in elastic/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.