01/21/2020, 1:37 AM
Is there any chance the pulimi team would rethink stacks? I mean, why can’t a stack be created as part of pulimi itself? Why is it an outside resource? Let me run pulumi up and define/create/use a stack directly before creating all the AWS resources. I feel like this is a missed opportunity. Now I gotta wrap all my Pulumi call in a CI build script (in Ruby) before actually calling pulimi up, would be nicer to do that as part of pulimi (in TS/Go whatever)


01/21/2020, 1:42 AM
Seems like you're asking for this:


01/21/2020, 1:43 AM
Not sure
It seems to overly complicate things. Just let me create or reference stack in one go within the API.
Copy code
let baseNetwork = new pulumi.Stack("pr-123", {
  config: {
    someStuff: "test", 
   secrets: {
     somePassword: process.env["password"]
if it doesn’t exist, it creates it. Every resource created after that is part of that stack.
I actually dislike the current design, my suggestion is an overhaul.


01/21/2020, 7:49 AM
What happens if you create two or zero stacks?