This message was deleted.

Thank for for the feedback, this is helpful. Regarding stack references, am I doing something incorrect?

variables:
  vpcId: ${shared-infrastructure.outputs["vpcId"]}


resources:
  shared-infrastructure:
    type: pulumi:pulumi:StackReference
    properties:
      name: ${sharedInfrastructureStackName}
    
  shared-vpc:
    type: aws:ec2/vpc:Vpc
    get:
      # This fails as a stack reference, but succeeds if I hardcode the VPC ID here
      id: ${vpcId}

That looks like what I would expect, a quick test you could do use take that yaml and run

pulumi convert --language typescript

and see what TS code it gives you and see if that program works as expected. If it does then it's probably a bug in the yaml runtime.

Looks incorrect:

const sharedInfrastructure = new pulumi.StackReference("shared-infrastructure", {name: sharedInfrastructureStackName});
const vpcId = sharedInfrastructure.outputs.vpcId;
const sharedVpc = new aws.ec2.Vpc("shared-vpc", {});

That does look wrong, can you open an issue at https://github.com/pulumi/pulumi-yaml/issues with those code snippets.

Yeah

I think the default is to output to the same directory, which does overwrite any Pulumi.yaml already there. Not sure if the sensible thing there is to default to something like --out=./out, require a prompt to say it's ok to overwrite or do like

pulumi new

and require --out to be empty. Worth raising another issue at https://github.com/pulumi/pulumi/issues to point out this UX is not ideal as is though, we can take some ideas of what would be the most preferable behaviour.

I would suggest either 1. A warning with prompt to continue, or 2. A default directory