hashicorp/packer

The -NonInteractive Parameter should be added by default when starting a powershell shell

Open

#12,637 opened on Sep 27, 2023

View on GitHub
 (3 comments) (2 reactions) (0 assignees)Go (3,228 forks)batch import
enhancementhelp wantedprovisioner/powershell

Repository metrics

Stars
 (13,697 stars)
PR merge metrics
 (Avg merge 5d 6h) (9 merged PRs in 30d)

Description

When a script called by the Powershell provisioner includes a command that involves a y/n prompt (or other kinds of interaction (e.g., Read-Host) the Powershell script will appear to hang as that script will wait indefinitely for the input. The -NonInteractive Parameter should be added by default when using the Powershell provisioner. This would result in an error instead of the apparent hanging when using commands requiring interactivity.

This can currently be worked around by specifying a custom execute_command, but it would be preferable to set the parameter by default.

Originally posted by @floh96 in https://github.com/hashicorp/packer/issues/4916#issuecomment-1239297541

Contributor guide

Research direction
Locate the PowerShell provisioner's execute command template in Packer's source code, and modify the default template to include the NonInteractive flag.
Tech stack
go
Domain
devops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55