I'm looking at this documentation: https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/automation/#LocalWorkspace Why is it that the static method

LocalWorkspace.createStack()

returns the promise of a

Stack

whereas if I make an instance of `LocalWorkspace`:

const workspace = LocalWorkspace.create({ /* ... */ });

workspace.createStack("somestackname")

here returns

void

? I was going to try a factory that dispensed workpsaces, but I'm wondering if this idea that I produce workspace instances is me misunderstanding the automation api fundamentals. If there is an example of using an instance of a localworkspace as opposed to just that classes static methods for creating at stack and returning information about it I would appreciate it

await workspace.stack()

returns a StackSummary type

@full-eve-52536 thank you for the reply. Are there methods to take an instance of a stack and do an

.up()

with it, or is this only available using the static methods

LocalWorkspace

I've myself have been only dabbling with the Pulumi automation API. As far as I know, the

up()

method exists on the

Stack

type objects. So something like this should work:

const stack = await workspace.selectStack(stackName);
await stack.up();

I think using the static method this would work, but for an instance

.selectStack

returns a

void

with typescript

Yeah I found it to be a little strange as well. Ultimately I ended up representing "instances" of

workspace

as

WorkspaceArgs

. I.e:

const workspaceArgs: LocalWorkspaceOptions = {
    workDir: infraDir,
    envVars: {
      PULUMI_K8S_ENABLE_PATCH_FORCE: 'true',
      NODE_OPTIONS: '',
    },
  };

I also see there is some option to supply a callback, maybe the idea is I do things more

async

and hit a callback