Azure / Azure/kubectl-aks

[RFE] Support interactive mode in `run-command`

Open
#25 0 comments 0 reactions 0 assignees View on GitHub
enhancement run-command
Dominant language
Go
Stars
39
Forks
15
PR merge metrics
No merged PRs in 30d

Description

## Current situation

The current implementation of `run-command` command has the following limitation:

> - Scripts that prompt for information (interactive mode) aren't supported.

Ref: https://learn.microsoft.com/en-us/azure/virtual-machines/linux/run-command#restrictions

## Ideal future situation

After implementing https://github.com/Azure/kubectl-az/issues/24, we could reuse that logic to support interactive mode. If we are not able to support it without passing through Kubernetes, then the `run-command` should first try the interactive mode and automatically fallback to non-interactive mode if it fails (Kubernetes control plane is down).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the run-command entry point and compare its current execution path with the interactive-mode logic requested in issue #24. Check the linked Azure Run Command restrictions and define how interactive success and Kubernetes control-plane failure should be recognized. Done means interactive prompts work and the documented fallback behavior is covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, go, kubernetes
Domain
cli, cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.