https://pulumi.com
Join Slack
Menu
Home
Archive
This message was deleted.
# typescript
s
This message was deleted.
l
The problem here is (I think) that vaultKey is an Output which contains undefined, and you're not checking for that. You don't need the current guard, you need one inside an apply.
Unfortunately, that means you'd be conditionally creating resources based on unknown values. The contract for getOutput says that it should return undefined, but it's not; I don't know if that's a bug in the docs or in the code, though.
You might be better off using 
requireOutput()
and aborting that way?
It might even throw a catchable exception, I'm not sure.
a
There error is about the non-existent stack
Copy code
pulumi:pulumi:Stack (iam-iam.dev):
    error: preview failed
 
  pulumi:pulumi:StackReference (vault-dev):
    error: Preview failed: unknown stack "vault-dev"
Until now, I've been keeping all of my IAM roles/instance profiles in one project and reference those in other projects. The issue I'm running into is with this project for a Vault stack. Originally, I defined the policy and attached the policy in the Vault project, but it's led to a situation where things get weird with a policy defined in the Vault stack being attached to a role defined in the IAM stack.
There's nothing stopping me from moving the Vault server role and whatnot to the Vault project besides my own desire for consistency
But to be clear, if the referenced stack doesn't exist, I want pulumi to ignore the code related to it
I found there is a 
forceDetachPolicies
option for 
aws.iam.Role
That solves the issue I was trying to work around
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by