This message was deleted.

--yes

does not automatically do this, and I don’t see a different flag for it.

Not on

up

, but we do have

pulumi stack select --create ...

to do this.

FWIW, I've noticed that the CLI crashes out in our CD environment unless

--non-interactive

is included, even with a previous

stack select

and

--yes

provided on

up

. There are examples that disable preview mode that may skip this code path, but the crash seems to be related to the progress bar. There might be something in our CI/CD environment that requires the

--non-interactive

option as it's not doced in CD guides https://www.pulumi.com/docs/guides/continuous-delivery/

panic: fatal: An assertion has failed: action must be non empty

goroutine 32 [running]:
<http://github.com/pulumi/pulumi/pkg/util/contract.failfast(...)|github.com/pulumi/pulumi/pkg/util/contract.failfast(...)>
	/home/travis/gopath/src/github.com/pulumi/pulumi/pkg/util/contract/failfast.go:23
<http://github.com/pulumi/pulumi/pkg/util/contract.Assertf(0x0|github.com/pulumi/pulumi/pkg/util/contract.Assertf(0x0>, 0x16d97be, 0x18, 0x0, 0x0, 0x0)
	/home/travis/gopath/src/github.com/pulumi/pulumi/pkg/util/contract/assert.go:33 +0x197
<http://github.com/pulumi/pulumi/pkg/backend/display.makeActionProgress(0x2659b50|github.com/pulumi/pulumi/pkg/backend/display.makeActionProgress(0x2659b50>, 0x1, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/home/travis/gopath/src/github.com/pulumi/pulumi/pkg/backend/display/progress.go:60 +0xe8
<http://github.com/pulumi/pulumi/pkg/backend/display.(*ProgressDisplay).refreshColumns(0xc001238000|github.com/pulumi/pulumi/pkg/backend/display.(*ProgressDisplay).refreshColumns(0xc001238000>, 0x2659b50, 0x1, 0xc0012cc230, 0x5, 0x5, 0xc0012c2d80, 0x5, 0x5)
	/home/travis/gopath/src/github.com/pulumi/pulumi/pkg/backend/display/progress.go:373 +0x10d
<http://github.com/pulumi/pulumi/pkg/backend/display.(*ProgressDisplay).refreshAllRowsIfInTerminal(0xc001238000)|github.com/pulumi/pulumi/pkg/backend/display.(*ProgressDisplay).refreshAllRowsIfInTerminal(0xc001238000)>
	/home/travis/gopath/src/github.com/pulumi/pulumi/pkg/backend/display/progress.go:591 +0x36e
<http://github.com/pulumi/pulumi/pkg/backend/display.(*ProgressDisplay).processNormalEvent(0xc001238000|github.com/pulumi/pulumi/pkg/backend/display.(*ProgressDisplay).processNormalEvent(0xc001238000>, 0x16c72e0, 0xc, 0x1559ec0, 0xc000aba640)
	/home/travis/gopath/src/github.com/pulumi/pulumi/pkg/backend/display/progress.go:966 +0x45a
<http://github.com/pulumi/pulumi/pkg/backend/display.(*ProgressDisplay).processEvents(0xc001238000|github.com/pulumi/pulumi/pkg/backend/display.(*ProgressDisplay).processEvents(0xc001238000>, 0xc000108050, 0xc000041020)
	/home/travis/gopath/src/github.com/pulumi/pulumi/pkg/backend/display/progress.go:1033 +0x13d
<http://github.com/pulumi/pulumi/pkg/backend/display.ShowProgressEvents.func1(0xc001238000|github.com/pulumi/pulumi/pkg/backend/display.ShowProgressEvents.func1(0xc001238000>, 0xc000108050, 0xc000041020, 0xc000394000)
	/home/travis/gopath/src/github.com/pulumi/pulumi/pkg/backend/display/progress.go:277 +0x3f
created by <http://github.com/pulumi/pulumi/pkg/backend/display.ShowProgressEvents|github.com/pulumi/pulumi/pkg/backend/display.ShowProgressEvents>
	/home/travis/gopath/src/github.com/pulumi/pulumi/pkg/backend/display/progress.go:276 +0x44b

@green-hydrogen-22278 that is surprising - and does look like a bug in the CLIs detection of whether it is in an interactive terminal. I’ll open an issue and make sure we can get this fixed.