Allow passing more than one context to an extension
- Dominant language
- TypeScript
- Stars
- 41
- Forks
- 24
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 56
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.
Contributor guide
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.
Assessment
- Tech stack
- elasticsearch, typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100