Any idea when the next Pulumi core release is planned for? Waiting on this change to fix Kubernetes deployment https://github.com/pulumi/pulumi/pull/5760

Hello, short question here: Is it possible to run

pulumi preview

without actually comparing against the current stack? I am trying to test if the pulumi code compiles without error in a CICD script, and at this point don't actually care about the changes it may or may not cause

One more CICD-related question: When getting the output of pulumi preview in a GitLab merge request, it seems that they get truncated (see the screenshot below). Is there a way to show the full output regardless of length?

Has anyone deployed a nextjs app with AWS?

We are still exploring CI/CD and have not find a way yet to print the output of

pulumi up

to the merge request overview on GitLab. The ressource changes from the

pulumi preview

show up properly (see image) but no output from

pulumi up

is added afterwards.. It would be good to get the output, since there are cases in which

pulumi up

throws some errors that are important to be notified of... Does anyone know a trick?

Is there a way to create a resource, but not delete it? AWS CloudFront's "Lambda@Edge" functions can be created, but AWS takes care of deleting them (and gives an error if pulumi tries to delete them instead). So is there some way to create these functions, but delete them?

Hey! Does anyone know how to import an existing kubernetes resource? I tried UID, name, and self link but nothing works...

hey folks! 👋 I’m looking into Pulumi to automate the creation of our users in AWS, but the question I have is not AWS-specific: What would be a best practice to output the temporary generated passwords out of pulumi? Would you say it’s ok to output them as plain text, assuming they’re only temporary and will need to be changed by user upon first login anyway? As we’re running Pulumi as part of an automated pipeline (using Codefresh), I guess I would still be a little uncomfortable to have those passwords leaking into the pipeline logs. Though we still need to retrieve those passwords somehow… 🤔

For those using pulumi within a CICD pipeline to provision an amazon EKS cluster, how do you communicate with the cluster after its creation (e.g. via kubectl) when the awscli is configured to use your personal AWS credentials?

Hi, I use GCP provider with Python. Its possible to store the output public IP addresses of the machines I created with GCE in a array? Thanks

I want to use

pulumi state delete

to remove a resource that is "pending delete". However, the URN refers to two resources. When I run

pulumi state delete

I get the following prompt:

Multiple resources with the given URN exist, please select the one to edit:  [Use arrows to move, enter to select, type to filter]
> "handle-request-ap-1782-resources-resources-ci-901d9e4"
  "handle-request-ap-1782-resources-resources-ci-b67bf05" (Pending Deletion)

Is there any way to select the second one non-interactively? I want to do this on my CI server.

Is there a way to define a default

orgName

so that I can use the shorthand for referring to a stack? So instead of having to write

pulumi stack select myorg/mystack

I can just define

myorg

as the default, and just do

pulumi stack select mystack

?

If I want to create an IAM policy with Pulumi that grants full access to resources that Pulumi manages, is there a way to just get all Pulumi-managed resources for the stack in one go?

Pulumi is suddenly very slow, an update took 1.5 hours. Any idea?

Dear community, how do you

pulumi destroy

via GitLab CI? Is it even possible? Cheers Robin

The name of the resources are generated in this form:

test-api-c0163d9

test-lambda-6e02bf9

How this hash is generated and how can I choose a string to replace it?

Is there some way to get a pulumi output set as an github action output when using the Pulumi Github Actions?

I got

Duplicate resource URN

error, but URN is unique. The URN is very long(->307), can that be the cause of the error?

How can I mock configuration?

Error: Missing required configuration variable 'project:domain'

running in NodeJS

are there any examples of mocking a stackreference?

how can we specify the

kubecontext

for a Helm chart resource?

Talk on that compared

pulumi

with other tools in

kubecon

https://kccncna20.sched.com/event/ek9o/five-hundred-twenty-five-thousand-six-hundred-k8s-clis-phillip-wittrock-gabbi-fisher-apple

anything like pulumi2tf available? use case: my org is currently bound by contract to supply tf scripts to our customers for infra on which our software suite is installed to even consider migrating to pulumi, we must first achieve the intermediate goal of generating same tf from equivalent pulumi

pardon if this is not an appropriate channel for this, but I am looking to bring on a devops engineer to help me promote and build a great devops culture. We are a small and young tech company that is really well funded. I and the dev team want Pulumi to be at the heart of our IaC! If interested, DM me for info. (not sure I’m allowed to post it here)

what's the recommended way to run shell commands with pulumi after a resource is created?

If I have a resource that contains a secret, then

pulumi update

will only show the details as

secret

. For example, on an AWS Task Definition:

~ containerDefinitions: "[secret]" => "[secret]"

I really want to see what's about to change on that

containerDefinition

. Is there a way to show those secret values?

is it possible to pass values from an API as configuration values to the Pulumi script? I don’t want to set the config values in the CLI mode, I am looking for a fully automated way without using CLI and the Pulumi script gets the value from another source and use it to do the provisioning.

Hello folks, When i am trying to create Ingress/Egress attribute of the SecurityGroup, it throws a following error

ingress=[aws.ec2.SecurityGroupIngressArgs(
    AttributeError: module 'pulumi_aws.ec2' has no attribute 'SecurityGroupIngressArgs'

The code was referred from an Pulumi docs example.

security_group = aws.ec2.SecurityGroup( # type: ignore
    "secgrp",
    description="Splunk Hybrid cloud security group",
    vpc_id=vpcid,
    ingress=[aws.ec2.SecurityGroupIngressArgs(
        description="TLS from VPC",
        from_port=443,
        to_port=443,
        protocol="tcp",
        cidr_blocks=["0.0.0.0/0"],
    )],
    egress=[aws.ec2.SecurityGroupEgressArgs(
        from_port=0,
        to_port=0,
        protocol="-1",
        cidr_blocks=["0.0.0.0/0"],
    )],
)

Any suggestions?

Ran into an issue today, looks like when creating a kubernetes secret with Pulumi you have no choice but to accept autonaming of the secret. https://github.com/pulumi/pulumi/issues/5790