Does the syntax theme that is shown on the Pulumi site exist? I looked everywhere and could not find it.

I want it really bad 👀

(Also, thank you for the Cloud Run provider you launched recently, super huge fan of Cloud Run and the combo of Pulumi + Cloud Run is incredible)

Is there any way to automatically create the stack when running

up

non-interactively?

How do you manage multi-step

Resource

configuration in Pulumi ? I'm trying to set up an SSO between Okta and AWS using Pulumi, and that requires 3 steps with 2

Resources

: 1. Create

<http://okta.App|okta.App>

which generates metadata 2. Inject metadata and create

aws.iam.IdentityProvider

, which has an ARN 3. Inject

IdentityProvider

ARN back into the

<http://okta.App|okta.App>

Resource created in step 1 I'm trying to pack this logic into a

Component

but I struggle with step 3: can't seem to update a

Resource

as part of a

Component

Also tried using

_import

but there's an URN conflict because the imported resource (step 3) would actually be the same as step 1... Should I try creating a Dynamic Provider for that ? Can't it be done natively ?

I'm new to Pulumi. Is there some way for Pulumi to wait a resource to be completely ready before querying information about the resource? I need to create AWS EKS and then to query the AWS EKS's vpc_config but there is a piece of information that is not available until AWS has completely created the EKS (the master plane security group).

i need to be able to throw an error during the preview step if a particular image tag doesn't exist in a particular docker repo so that we can reject a pull request which will ultimately fail. can anybody suggest a good way of doing this? is it going to be a matter of writing a dynamic provider?

I've read and re-read about Output types but it's still not clicking for me. I'm trying to create an array, but keep getting the error about o.apply.

let vpcList = vpcConfig.map(entry => {
        return new aws.ec2.Vpc(entry.name, {cidrBlock: entry.cidrBlock, tags: {Name: entry.name}});
    });

    let vpcNameToId: { [index: string]: any } = {};
    for (let vpc of vpcList) {
        // create a lookup
        const vpcName = vpc.tags.apply(v => v?.Name ?? null);
        vpcName.apply(theName => {
            console.log("Applying " + theName + "=" + vpc.id.apply(v => `${v}`));
            // vpcNameToId[theName] = vpcId;
        });
    }

Results in:

Applying vpc0=Calling [toString] on an [Output<T>] is not supported.
    To get the value of an Output<T> as an Output<string> consider either:
    1: o.apply(v => `prefix${v}suffix`)
    2: pulumi.interpolate `prefix${v}suffix`
    See <https://pulumi.io/help/outputs> for more details.
    This function may throw in a future version of @pulumi/pulumi.

is there an RSS feed for changelog on pulumi? I'd love to subscribe it to my slack

Hi guys! I want to use this module https://github.com/pulumi/pulumi-postgresql to create roles and grants for GCP CloudPostgre Instances. My SDK is Python and I use

pulumi-gcp

module to create a CloudSQL DB Instance https://github.com/pulumi/pulumi-gcp/blob/master/sdk/python/pulumi_gcp/sql/database_instance.py. Since

pulumi-postgresql

connects to an instance similarly to pgsql, I define

PGHOST

,

PGUSER

, and

PGPASSWORD

during Pulumi runtime. Since the CloudSQL Instance is created via the same execution, I define dependencies like:

opts=ResourceOptions(
                depends_on=[cloud_pgsql_main_1],
            ),

Nevertheless, it doesn't seem to work as it tries to connect to the instance immediately, however the instance is obviously not ready, and

pulumi up

fails. Do you think it is possible that two separate modules

pulumi-gcp

and

pulumi-postgresql

do not appropriately share dependencies during runtime?

Don't suppose someone could help me out with my issue, please? https://github.com/pulumi/pulumi/issues/3919

i was using pulumi last year to deploy a project, and i was doing

pulumi.runtime.listResourceOutputs(k8s.apps.v1.Deployment.isInstance)

to collect information about the currently-deployed deployments. that project was shelved, and when i came back to it recently i discovered that it no longer works. i see that signature now asks for a type, so I gave it

k8s.apps.v1.Deployment

but it still fails. does anyone know why this might be?

ohai, I submitted a Pulumi Support/Contact request like 2-3 weeks ago because I’m interested in migrating our org to the new billing model w/unlimited stacks, but I haven’t yet heard from a Pulumi rep. What do?

hey all, having trouble getting an ecs service definition to work using pulumi/awsx in js. my service definition looks like:

let appVpc = aws.ec2.getVpc({id: "my-vpc-id"});

const webServerLoadBalancer = new awsx.lb.ApplicationLoadBalancer("web-server-lb-" + userEnv, {
    securityGroups: [],
    vpc: appVpc,
    subnets: ["subnet-1", "subnet-2", "subnet-3"]
});

const webServerLoadBalancerListener = webServerLoadBalancer.createListener("ws-https-" + userEnv, {
    port: 443,
    protocol: "HTTPS",
    certificateArn: "my-cert-arn"
});

const webServerLoadBalancerRedirectToHttpsListener = webServerLoadBalancer.createListener("ws-redirect-to-https", {
    port: 80,
    protocol: "HTTP",
    defaultAction: {
        type: "redirect",
        redirect: {
            protocol: "HTTPS",
            port: "443",
            statusCode: "HTTP_301"
        }
    }
});

const webServerCluster = new awsx.ecs.Cluster("web-server-" + userEnv, {
    securityGroups: ["sg-1"],
    vpc: appVpc
});

const webServerFargateService = new awsx.ecs.FargateService("web-server-" + userEnv, {
    cluster: webServerCluster,
    networkConfiguration: {
        subnets: ["subnet-1", "subnet-2", "subnet-3"]
    },
    taskDefinitionArgs: {
        containers: {
            webServer: {
                image: "my-org/web-server:" + userEnv,
                portMappings: [
                    webServerLoadBalancerListener
                ],
                healthCheck: {...healthCheckArgs}
            }
        }
    }
});

the error I’m receiving is that

error: aws:ecs/service:Service resource 'web-server-dev' has a problem: "network_configuration.0.subnets": required field is not set

, which doesn’t make sense to me. per the docs, I’m setting the

networkConfiguration

property of the service, and I’m tried both wrapping that property in an array and as an object. no dice either way. any thoughts?

Hi all. I'm struggling with something that seems like a pretty simple variation on an example from the docs. I'd appreciate any help if you see where I'm going wrong. I'm trying to create a "Fire & Forget" task using a CloudWatch event and a FargateTaskDefinition. I'm basing my attempt on this example: https://www.pulumi.com/docs/guides/crosswalk/aws/ecs/#running-fire-and-forget-tasks So, here's what I have:

// create  cluster
const cluster = new awsx.ecs.Cluster(`cluster`, {
  name: `demo-cluster`
});

// create image
const img = awsx.ecs.Image.fromDockerBuild(`image`, {
  context: './app',
});

// create task
const task = new awsx.ecs.FargateTaskDefinition(`task`, {
  container: {
    image: img,
    memoryReservation: 2048
  }
});

// create the cloudwatch event and lambda function using the "onSchedule" helper function
aws.cloudwatch.onSchedule(`task-schedule`, 'rate(5 minutes)',
  async (req) => {
    // run the task in our cluster
    const result = await task.run({cluster});
    return { statusCode: 200, body: "OK" };
  }
);

Everything seems to build and deploy to AWS correctly. I see the Lambda function, CloudWatch event, logs, task definition, etc. It's all there and linked up. And when I look at my CloudWatch logs for that Lambda function, I see that it's attempting to run every 5 minutes. However, I'm getting this error when it runs:

{
  "errorType": "Runtime.ImportModuleError",
  "errorMessage": "Error: Cannot find module '@pulumi/awsx/ecs/index.js'\nRequire stack:\n- /var/task/__index.js\n- /var/runtime/UserFunction.js\n- /var/runtime/index.js",
  "stack": [
    "Runtime.ImportModuleError: Error: Cannot find module '@pulumi/awsx/ecs/index.js'",
    "Require stack:",
    "- /var/task/__index.js",
    "- /var/runtime/UserFunction.js",
    "- /var/runtime/index.js",
    "    at _loadUserApp (/var/runtime/UserFunction.js:100:13)",
    "    at Object.module.exports.load (/var/runtime/UserFunction.js:140:17)",
    "    at Object.<anonymous> (/var/runtime/index.js:43:30)",
    "    at Module._compile (internal/modules/cjs/loader.js:955:30)",
    "    at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)",
    "    at Module.load (internal/modules/cjs/loader.js:811:32)",
    "    at Function.Module._load (internal/modules/cjs/loader.js:723:14)",
    "    at Function.Module.runMain (internal/modules/cjs/loader.js:1043:10)",
    "    at internal/main/run_main_module.js:17:11"
  ]
}

During the Pulumi "magic" of packaging and building the Lambda handler, it looks like it's telling Lambda to look for some Pulumi modules that aren't installed. Any ideas on why this is happening? Thank you, thank you!!

Okay, I'm refining my previous issue with what I've learned. The problem seems to be when I reference the

task

in the Lamdba callback that I'm creating with

onSchedule

. So, this DOES work:

const task = new awsx.ecs.FargateTaskDefinition(`task`, {
  container: {
    image: img,
    memoryReservation: 2048
  }
});

aws.cloudwatch.onSchedule(`task-schedule`, 'rate(5 minutes)',
  async (req) => {
    console.log('Is this thing on?')
    return { statusCode: 200, body: "OK" };
  }
);

But as soon as I reference the

task

in the callback, I get errors about missing modules. Even if I'm not trying to run the task:

aws.cloudwatch.onSchedule(`task-schedule`, 'rate(5 minutes)',
  async (req) => {
    console.log(task); // just try to log the object -- don't even try to run it
    return { statusCode: 200, body: "OK" };
  }
);

This is the error that Lambda throws when it tries to run the callback:

{
    "errorType": "Runtime.ImportModuleError",
    "errorMessage": "Error: Cannot find module '@pulumi/awsx/ecs/index.js'\nRequire stack:\n- /var/task/__index.js\n- /var/runtime/UserFunction.js\n- /var/runtime/index.js",
    ...
}

So, it seems like is's an issue with how Pulumi is packaging the Lambda function, right? I'll add that the container image doesn't contain any references to Pulumi or dependencies, so the error probably isn't related to the image. I'm using the same image on other Fargate Services created by Pulumi, and it's running fine.

is there any way to use an existing ecr image with awsx fargate? the awsx container definition expects for the

image

property something that implements

ContainerImageProvider

, but there’s no way in

awsx.ecr

to actually pull an existing image – only to create one via

buildAndPushImage

. if I use

aws.ecr.getImage

, it returns a

getImageResult

which is incompatible as it doesn’t implement

ContainerImageProvider

We have started to use Pulumi and it's been mostly smooth, just some issues with EKS etc. But today I realized something that is considerably more difficult in Pulumi than in Terraform. When I create resources in Terraform I know exactly the resource name to query. This seems not be the case with Pulumi since it appends its own postfix to resource names. E.g. if I create an AWS Secret using terraform I know in my application code later on that the key is e.g. "dev-rds-password". But with Pulumi I don't know this in application code since the name is something like "dev-rds-password-b229d59" and in application code I have no idea what the postfix is. Is there some pattern for this? For now I need to look all AWS Secrets and check the tag values to find the right secret and find its name and only then I can query the secret value using that resource name.

Nearing release of my Application to the world...Built entirely on Pulumi! Thanks team for everything!!!

Hi everyone, I have an extremly important question which is driving me mad: What is the origin for the name Pulumi? Google Translate seems to suggest that is Hawaiin for a Burmese but I'm not sure that is it. Any enlightenment would be greatly appreciated 🤪

is there a way to get the IAM account for the current user?

Im interested in using pulumi at runtime to dynamically CRUD cloud resources - anyone have some simular experiences, including dealing with the state or recreating/refreshing the state from scratch each invocation?

Hi new to Pulumi. In typescript can I log my own messages to the pulumi console?

hi all, i'm trying out pulumi and are creating some new projects. but i cannot delete them from pulumis memory 🙂 pulumi new [sdk] create a project(workspace?) with default name of the folder you are inside. but how do I delete this project so that i can reuse the name? i have of course deleted the folder already

how do people handle versioning their stacks by environment? I have let’s say a dev environment. when I want to spin up a prod environment, I’d like to keep the dev environment as opposed to deleting all the dev resources before spinning up a prod env

What are the plans for

pulumi-awsx

for python? I see its 13 months stagnant. Do you have design docs which you follow for each of these projects? Looking at the node one, it looks like structure and patterns may have changed a bit.

Updating from @pulumi/eks 0.18.18 to 0.18.21 results in Pulumi thinking all (I think?) of my k8s resources need to be replaced. This seems like a regression, given nothing in the eks changelog (https://github.com/pulumi/pulumi-eks/blob/master/CHANGELOG.md) indicates that this should occur.

I am using the azure devops task, is there anyway of outputing permalink as a variable?

question: Is it a reasonable assumption that as a stack gets larger that changes made to the stack start slowing down?

Hi All, I am trying to create Dynamic Provider and on executing it via 'Pulumi up' command, I am getting an error"

pulumi-python:dynamic:Resource :

error: Exception calling application: There is no current event loop in thread 'ThreadPoolExecutor-0_0'.