cloudtools/stacker

Should interactive mode ask you about creating new stacks?

Open

#569 opened on Mar 16, 2018

View on GitHub
 (3 comments) (1 reaction) (0 assignees)Python (706 stars) (166 forks)batch import
enhancementgood first issuehelp wanted

Description

The current behavior of --interactive is that any new stacks will get created, without any prompt. But this can be potentially dangerous (or at the very least, annoying) if you accidentally make a change, like changing the stack name, resulting in a whole new stack getting created.

Should stacker prompt you before creating a stack when using --interactive mode?

Contributor guide

Tech stack
pythonaws
Domain
cliclouddevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
Examine the interactive mode implementation in stacker/commands.py or similar CLI entry points. Look for where ' interactive' flag is handled and where new stacks are created without confirmation. The goal is to add a prompt (e.g., using input() or click.confirm()) before creating a stack when in interactive mode. Consider also adding a ' yes' flag to skip the prompt. Review existing tests for interactive mode in the test directory.