Just to know, exists any language syntax easy to create our iac code using a easy language like hcl (terraform) for pulumi ?

Also, is possible to use Ruby on Pulumi to create our own code ?. Please, show me how. 🙏

Hi Guys! We urgently need support from the Pulumi Dev Team. We have a storage container deleted from the account, although we have not instructed this anywhere. The project is the bootleneck of our project that is supposed to go live on Monday.

what's a good way to organize code that belongs to one stack, but no other stacks? as a for instance, we have a codebuild job that does two different things in staging/production, was kinda curious how people approached that

hello I’d like to use

@aws-sdk

in a pulumi script but the code tries to run during the preview mode, how to make it behave like regular pulumi resources ?

any ideas how to change an aws default resource tag without having to re-create all resources?

Hello! I have a general understanding of Project and Stacks. My problem is in my Dev and Prod stack I need to provision it to different AWS regions and they have some differences between each other. How do I go about setting that up and how do I set up the CI/CD pipeline? The Dev and Prod stack corresponds to a Dev and Prod git branch correct?

Does pulumi support creating a self managed k8s cluster?

Does pulumi support Helmfile?

hey folks, what is a proven-practice to wait for userData script to complete. We currently the problem that pulumi shuts-down instances too early when replaced, because the userData script still runs. 😞 My favorite way would be that I can have pulumi shut down the old instances and replace ips in lb only once the new userData is done

Hey there - is there a GitLab-CI YAML provider? Something like https://www.pulumi.com/learn/pulumi-fundamentals/create-docker-images/ but for GitLab pipelines development? I see https://www.pulumi.com/registry/packages/gitlab/ which manages GitLab resources, which is awesome; but not quite I'm looking for. I'm looking for a Pulumi-assisted way to building (dynamic?) GitLab-CI yaml pipelines. Same idea: use a high-level programming language to build pipelines instead of writing

gitlab-ci.yml

YAML in the DSL To make my life easier, I've stumbled on: https://github.com/firecow/gitlab-ci-local - ideally I could compile a Pulumi program to generate the

gitlab-ci.yml

and then run it locally for faster/debug-friendly dev cycles. Any alternatives?

What's the closest thing to terraform modules in Pulumi? Compared to a TF module, building a component via this repo(https://github.com/pulumi/pulumi-component-provider-ts-boilerplate) seems like there's quite a bit of overhead or extra work. Is there a simpler option, possibly at the cost of it being less multi-lingual?

Hi, I am deploying virtual machine using automation api . While testing and deploying machine there was panic . Now when I try to either delete stack or create new machine I get following error

error: could not create stack: the stack is currently locked by 1 lock(s). Either wait for the other process(es) to end or manually delete the lock file(s).

Just wondering how I can manage and check if the stack is lock and manage it using automation api , instead of the deleting the stack file manually .

Hello, I am currently configuring an aws network with pulumi. I have a question. I already have a subnet created. cidr crash when resource_name is changed. Is there any way to solve this?

# example code
from pulumi import ResourceOptions
import pulumi_aws as aws

aws_vpc = aws.ec2.Vpc(
    'my-vpc',
    cidr_block    = '10.0.0.0/16',
    tags          = default_tags
    )

aws_public_subnet = aws.ec2.Subnet(
        resource_name     = 'public-subnet-change', # <= Originally a "public-subnet"
        vpc_id            = aws_vpc.id,
        cidr_block        = '10.0.1.0/24',
        availability_zone = 'ap-northeast-2a',
        tags              = default_tags,
        opts              = ResourceOptions(delete_before_replace=True)
    )

Do you want to perform this update? yes Updating (dev): Type Name Status Info pulumipulumiStack pulumi-demo-dev failed 1 error + └─ awsec2Subnet public-subnet-change creating failed 1 error Diagnostics: pulumipulumiStack (pulumi-demo-dev): error: update failed awsec2Subnet (public-subnet-change): error: 1 error occurred: * error creating EC2 Subnet: InvalidSubnet.Conflict: The CIDR ‘10.0.1.0/24’ conflicts with another subnet status code: 400, request id: *

Hi all ! What would be the best approach of creating NodeGroups using EKS with some additional commands to run during bootstrap. I have tried a number of approaches provided by Pulumi but none of them seem to be working out. Using the AWS Classic package: • No feature to add any additional bootstrap commands Using the pulumi_eks package: • Using NodeGroups option will bring up the NodeGroups but the instances are not attached to the Cluster (Launch configuration does contain the commands though) • Using ManagedNodeGroups, Additional bootstrap commands not added to the launch template Would appreciate some guidance with this problem.

Using Pulumi to deploy multiple docker container to Linux on Azure App Service. Working like a charm. Can't seem to figure out how to pass arguments (port and volume mappings) though. Any experience or ideas?

Hi I am new to pulumi and I have managed to import and thereby bootstrap our MS Azure environment. Now I would like to do the same with our existing vsphere environment. But I found that I cannot even start a new pulumi vsphere stack? ‘pulumi new’ does not show a vsphere option? How does one go about bootstrapping a vsphere stack then? And my next question is going to be can I still import an existing vsphere environment into the newlly created vsphere stack to bootstrap and ease myself into even fuller pulumi adoption of our already up and running environments?

I'm playing with the

pulumi-component-provider-go-boilerplate

repo. I built it and I executed the examples/simple stack. AWS resources are correctly created. Then I extended the code to register a resource transformation to tag the created AWS resources, based on this article. But it seems the transformation is not applied when I pass it to the

StaticPage

component using the key

transformations:

in

opts

, nor when using

pulumi.runtime.registerStackTransformation

. Are resource transformations in combination with component providers not supported?

Anyone have any recommendations for creating local files, something similar to terraform local file? https://registry.terraform.io/providers/hashicorp/local/latest/docs/resources/file Only thing I’ve found so far is using command and echoing

Hello! I want to deploy a new Deployment to an existing Kubernetes cluster in GCP. My company has no integration with Pulumi and I wanted to introduce them to this awesome product. My doubts are: 1. Is it possible to do it? I've said Deployment but there are actually a few more resources needed in a dedicated namespace. I intended to deploy all via pulumi. 2. Is there any chance of affecting the currently deployed cluster? 3. Could you provide any documentation on how to begin this integration? I have looked into this documentation (https://www.pulumi.com/docs/guides/adopting/#coexistence) but could find anything related to GCP.

Hi, is there a way to build multi-arch Docker images with Pulumi? I've spent quite some time experimenting but without success. I set up QEMU and Docker Buildx before running Pulumi so I can build images for multiple architectures using

extra_options

supplied to

DockerBuild

, e.g.

image = docker.Image(
    "image-arm64",
    build=docker.DockerBuild(
        context="..",
        extra_options=[
            "--platform=linux/arm64",
            "--output=type=docker",
            "--cache-from=type=local,src=/tmp/.buildx-cache",
            "--cache-to=type=local,mode=max,dest=/tmp/.buildx-cache",
        ],
    ),
    image_name=repository.repository_url.apply(lambda url: f"{url}:arm64"),
    registry=registry,
    skip_push=False,
)

The first problem is that I can only build image for one architecture a time and can't use multiple values for

--platform

(e.g.

--platform=linux/amd64,linux/arm64

) because: • I have to use the

docker

output type as Pulumi uses

docker inspect

after building the image (https://github.com/pulumi/pulumi-docker/blob/e2a25c62efc553515e784c0b241a2c946c888dd7/sdk/python/pulumi_docker/docker.py#L441). • The

docker

export type currently doesn't support multi-arch images (https://docs.docker.com/engine/reference/commandline/buildx_build/). Even if I build images for distinct platforms separately, I'd need a way to create and push the manifest list (https://docs.aws.amazon.com/AmazonECR/latest/userguide/docker-push-multi-architecture-image.html). There's no such resource in the Docker provider, though. For the motivation. I have a web app deployed as an ECS service running on AWS Fargate with autoscaling. I want to use a mix of Fargate and Fargate Spot, for tasks running on Fargate I'd like to use ARM64 architecture however Fargate Spot currently only supports x86-64 (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-capacity-providers.html).

Hello everyone! I need to set the environment for a newly created project on GCP account. I have to create a service account and enable certain roles/principals. Any examples or link in this regard? The sample example of service account creation gives the following error.

I'm using https://www.pulumi.com/registry/packages/random/api-docs/randompassword/ but not sure how to read out the secret that gets produced? Am I thinking about this wrong? I am setting up an RDS instance

hello everyone, I am looking to deploy postgres on GCP with cross region replicas. I wasn’t able to find anything in the docs. Are cross-region replicas possible with pulumi?

when doing an update to an existing stack I am seeing the following when updating an gateway2.Integration:

test-integ (aws:apigatewayv2:Integration)

error: aws:apigatewayv2/integration:Integration resource 'test-integ' has a problem: expected passthrough_behavior to be one of [WHEN_NO_MATCH NEVER WHEN_NO_TEMPLATES], got . Examine values at 'Integration.PassthroughBehavior'.

but initial deployment works fine. https://www.pulumi.com/registry/packages/aws/api-docs/apigatewayv2/integration/ describes PassthroughBehavior as only supported for WebSocket APIs but I'm creating an HTTP API. is this a bug?

Hello!. Whatever resource I try to create (am creating a lot i.e AKS, VM.Postgres, mlflow e.t.c) am just able to see only 2 resources in my pulumi up run ( Storage Account & Resource group) what am I missing? or the rest never shown?

Or am experimenting with free azure credit that doesn't allow this🤷‍♂️

Hi I am currently evaluating pulumi for my organisation. Is it possible to create a project with my indivdual account and then further down the line move the project to a collaborative organisation when I upgrade the account

is there a way to specify the state backend with code/config rather than run the

pulumi login

command?

is it possible yet to reference a stack in another backend? e.g. two different S3 buckets