hi, can you let me know about the pricing of the Enterprise plan?

I am reaching out regarding an issue we are facing with our Pulumi .NET automation. We have configured the working directory to be set from our .NET Core 6 project, and we call the

CreateOrSelectStackAsync

function. Our application is hosted on Kubernetes (K8s), and we keep encountering the following error message: "errorMessage": "An error occurred trying to start process 'pulumi' with working directory '/tmp/pulumi'. No such file or directory". However, we have verified that the folder path exists in the pod, and the "tmp" folder has the necessary permissions. We have set up the working directory as follows: var stackArgs = new InlineProgramArgs(PulumiConfigurationConstants.ProjectName, environment, program) { StackSettings = new Dictionary<string, StackSettings> { [environment] = new() { SecretsProvider = PulumiConfigurationConstants.SecretsProvider } }, SecretsProvider = PulumiConfigurationConstants.SecretsProvider, ProjectSettings = new ProjectSettings(PulumiConfigurationConstants.ProjectName, ProjectRuntimeName.Dotnet) { Backend = new ProjectBackend { Url = PulumiConfigurationConstants.PulumiProjectBackendUrl } }, WorkDir = Path.Combine("..", "tmp", "pulumi") }; var stack = await LocalWorkspace.CreateOrSelectStackAsync(stackArgs); I have also confirmed that the file is generated in the

/tmp/pulumi

directory. We would greatly appreciate any assistance you can provide in resolving this issue. Thank you for your attention to this matter.

Hi all Any solution for

Argument of type 'Output<string>' is not assignable to parameter of type 'string'

Hello everyone. I have some resources especially task Definitions that I have manually deleted on my aws ecs console page. Now that I’m trying to destroy all resources (

pulumi destroy -s <my-stack>

), I can’t get them destroyed as it can’t successfully delete those resources that I’ve manually deleted on the aws console. I also tried to delete the stack entirely (

pulumi stack rm <my-stack>

), and it’s the same error I’m getting. Please see image below for more info:

Hello together, hope that i can post here my problem 🙂. I try to use https://www.pulumi.com/registry/packages/azure-native/api-docs/containerregistry/task/#azure-native-containerregistry-task for creating a task which deletes images with a custom cmd with a schedule all 90days. I tried the docu but on the examples it says coming soon. Also the pulumi AI dont give me a good answer with which i can work. Iam working on this since a couple of days now. But now working solution in sight. Is there any example which i can follow to master this task? Or does anybody have on? Or can give me hints for what iam searching? Ah it is in GoLang. 🙂

👋 Hi everyone! Great to be a part of the Pulumi community. Been a fan since 2021, got a chance to work on it at last in my company this year. So, excited to ask a lot of questions and interact with a lot of you guys here in the community. 🤩

Does Fargate Crosswalk support non-default VPCs? Trying to deploy into a non-Default VPC kept giving me errors regarding mismatch VPCs, always showing the default VPC id versus the non-default one I have attached to all the resources I gave it (subnets, target groups, etc). Somewhere it's setting defaults or making assumptions it should not?

I understand the code behind dynamic providers is serialized and stored somewhere, how do I update this code? The API the provider integrates with has a breaking change that's preventing the old serialized version from working. I've updated my local code but running up again still behaves as if its running the old provider code. I'm running via the automation api, if that helps?

I renamed a stack project: from:

pulumi stack rename org/projectOLD/sand

to:

pulumi stack rename org/projectNEW/sand

but then the /prod stack disappeared though I still see it in Pulumi webUI I tried importing it back w/

pulumi -v 3 stack import -s org/projectOLD/prod

though the CLI just hangs and displays no logs. anyone has any suggestions?

how to execute docker images through pulumi

Hello, are there any plans to improve Gitlab integration with preview? Currently every preview job run create new MR comment. For instance MegaLinter also has MR decoration but instead of adding new comment it edit previous comment.

Hello Team, I am currently working on a project to design a CI/CD process for managing account-level database objects (such as users, roles, databases) using Pulumi. To refine our approach, I'm looking for insights from those who have experience with similar projects. Could you kindly share the Git workflows you have found to be most effective for this task? Additionally, I'm curious about the branching strategies that have worked well in your experience. I truly appreciate your time and assistance.

Hello, What would be the general process for creating a public provider that would be converted to all supported languages. For example, https://www.pulumi.com/registry/packages/cloudflare/ If I also wanted a public registry, how would one do this? Should I make terraform a provider first? Can I do this purely in TS and generate the provider for other languages?

Is there a way to check using the pulumi CLI if a resource in a stack is protected or not? From searching around I can't find an answer to this and none of the

Flags

listed seem to do it.

Hi everyone, I am trying to delete the default VPC using Sdk I see that code

import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";

// Delete the default VPC
const defaultVpc = new aws.ec2.DefaultVpc("defaultVpc", {
  forceDestroy: true,
});

and run

pulumi up

, the result is nothing happen. try to run

pulumi destroy

throw and error dependencies what I do wrong please?

Hello Everyone! Is there someone who knows when the Pulumi Update Plans go into General Availability? https://www.pulumi.com/blog/announcing-public-preview-update-plans/

hey there, I'm in the process of upgrading to the latest pulumi_auth0 version and following the https://github.com/auth0/terraform-provider-auth0/blob/main/MIGRATION_GUIDE.md to set up the appropriate new resources, but after doing a

pulumi up

I still get the same warnings. The state file still has the values in the same place, so I'm wondering if this is just stale data in the state? tried doing

pulumi up --refresh

hoping this will pull in fresh data without those values, but they seem to just stay there.. Is there a way to clear these warnings for resources that have been migrated?

Hi, hope you dont mind me posting a new user question here, I'm just trying pulumi out. I created a simple

Pulumi.yaml

which creates 100 aws providers, and 100 aws buckets based off those providers - as I have this usecase, and I would like to see how Pulumi handles it -

pulumi up

seems like it will take hours to run - it starts off by slowly (once every 10 seconds) creating each of the 100 providers in sequence - is this what you would expect? Am I missing some parallelism or "go faster" flag?

Hi I had a question about creating a Snowflake python UDF with Pulumi. I am getting this error with my resource definition:

SQL compilation error: An active warehouse is required for creating Python UDFs

but I don’t see where a warehouse can be specified in the Snowflake Function code:

class Function(pulumi.CustomResource):
    @overload
    def __init__(__self__,
                 resource_name: str,
                 opts: Optional[pulumi.ResourceOptions] = None,
                 arguments: Optional[pulumi.Input[Sequence[pulumi.Input[pulumi.InputType['FunctionArgumentArgs']]]]] = None,
                 comment: Optional[pulumi.Input[str]] = None,
                 database: Optional[pulumi.Input[str]] = None,
                 handler: Optional[pulumi.Input[str]] = None,
                 imports: Optional[pulumi.Input[Sequence[pulumi.Input[str]]]] = None,
                 language: Optional[pulumi.Input[str]] = None,
                 name: Optional[pulumi.Input[str]] = None,
                 null_input_behavior: Optional[pulumi.Input[str]] = None,
                 packages: Optional[pulumi.Input[Sequence[pulumi.Input[str]]]] = None,
                 return_behavior: Optional[pulumi.Input[str]] = None,
                 return_type: Optional[pulumi.Input[str]] = None,
                 runtime_version: Optional[pulumi.Input[str]] = None,
                 schema: Optional[pulumi.Input[str]] = None,
                 statement: Optional[pulumi.Input[str]] = None,
                 target_path: Optional[pulumi.Input[str]] = None,
                 __props__=None):

how can I set a warehouse for this case?

I'm using the nodejs

@pulumi/cloudflare

package and a couple of things I noticed: • for a WorkerScript, the full

content

of the script is stored in the state. Shouldn't this be a digest? • It keeps detecting a diff on

secretTextBindings

on each up Is this a pulumi issue, or something to be raised upstream? Thanks 🙏

Any upcoming pulumi sessions are there ? and i am thinking like when pulumi will rollout the certifications

Are we expecting resources to manage Dataform release configurations and/or workflow configurations in GCP? AFAIK there is currently no support for them

Anyone know what could be causing this message

warning: Found legacy stack files in state store:
  - dev
Please run 'pulumi state upgrade' to migrate them to the new format.
Set PULUMI_SELF_MANAGED_STATE_NO_LEGACY_WARNING=1 to disable this warning.

if both users working on a repo containing the .pulumi folder use the same version of pulumi (3.63.0). user A created and pushed to the repo and can deploy and view resources just fine. user B cloned the repo and gets the above error whenever trying to interact with any stack. i have no idea where a legacy stack file could could be coming from.

Good morning, We have an infrastructure managed with pulumi, in typescript, is it possible to integrate pulumi in argocd or fluxcd to manage our infrastructure? Thanks

I am following the strategy for enforcing resource tagging (https://www.pulumi.com/blog/automatically-enforcing-aws-resource-tagging-policies/) and one of those tags is the git commit hash. When a resource is updated I want the tag to be updated to the current commit hash but I don’t want a new commit to cause a change to the tag of every resource. Is this possible? I want something like a transformer that only applies when there is some other change.

I'm having some trouble where Pulumi states are being created using the legacy style. In particular, this is happening when using a local file backend in my test environments.

pulumi stack select dev --create

is creating a legacy stack, though my pulumi version is

v3.69.0

and I am deleting my

~/.pulumi

folder between runs. Is there a way to force always using the multi-project backend and never use the legacy style?

Coming from AWS CDK + CDK8s, pulumi stacks are kind of lost on me. As far as I understand, pulumi stacks are just environment specific configs, no differences in codebase., it all points to the same

index.ts

entry point. With CDK I was able to copy paste a class and change it's inputs to create an entirely different environment. With Pulumi I need to use multiple projects + envs and use stack references? (which seems weakly typed in terms of outputs)

How do I use

pulumi stack

command to view the information of a stack created through Pulumi Automation API? I'm able to remove/delete the stack, but when I want to select or view history of the stack, the command is failing expecting for a

Pulumi.yaml

file.

Is there a recommended workaround for this problem? How are others dealing with dependencies on CRDs loaded as a

CustomResource

? https://github.com/pulumi/pulumi-kubernetes/issues/1833

Pulumi Python AWS: AttributeError: type object 'Output' has no attribute 'json_dumps' I use the Pulumi sample code at https://github.com/pulumi/examples/tree/master/aws-py-apigateway-lambda-serverless. pulumi version v3.69.0 It runs on AWS cloud. I got errors as follows: main.py", line 49, in body=pulumi.Output.json_dumps({ AttributeError: type object 'Output' has no attribute 'json_dumps' Here is the code:

cat __main__.py
"""An AWS Python Pulumi program"""
import json
import iam
import pulumi
import pulumi_aws as aws

#region = 'us-west-2'
region = aws.config.region

custom_stage_name = 'example'

##################
## Lambda Function
##################

# Create a Lambda function, using code from the `./app` folder.

lambda_func = aws.lambda_.Function("mylambda",
    role=iam.lambda_role.arn,
    runtime="python3.7",
    handler="hello.handler",
    code=pulumi.AssetArchive({
        '.': pulumi.FileArchive('./hello_lambda')
    })
)


####################################################################
##
## API Gateway REST API (API Gateway V1 / original)
##    /{proxy+} - passes all requests through to the lambda function
##
####################################################################

# Create a single Swagger spec route handler for a Lambda function.
def swagger_route_handler(arn):
    return ({
        "x-amazon-apigateway-any-method": {
            "x-amazon-apigateway-integration": {
                "uri": pulumi.Output.format('arn:aws:apigateway:{0}:lambda:path/2015-03-31/functions/{1}/invocations', region, arn),
                "passthroughBehavior": "when_no_match",
                "httpMethod": "POST",
                "type": "aws_proxy",
            },
        },
    })

# Create the API Gateway Rest API, using a swagger spec.
rest_api = aws.apigateway.RestApi("api",
    body=pulumi.Output.json_dumps({
        "swagger": "2.0",
        "info": {"title": "api", "version": "1.0"},
        "paths": {
            "/{proxy+}": swagger_route_handler(lambda_func.arn),
        },
    }))

# Create a deployment of the Rest API.
deployment = aws.apigateway.Deployment("api-deployment",
    rest_api=rest_api.id,
    # Note: Set to empty to avoid creating an implicit stage, we'll create it
    # explicitly below instead.
    stage_name="",
)

# Create a stage, which is an addressable instance of the Rest API. Set it to point at the latest deployment.
stage = aws.apigateway.Stage("api-stage",
    rest_api=rest_api.id,
    deployment=deployment.id,
    stage_name=custom_stage_name,
)

# Give permissions from API Gateway to invoke the Lambda
rest_invoke_permission = aws.lambda_.Permission("api-rest-lambda-permission",
    action="lambda:invokeFunction",
    function=lambda_func.name,
    principal="<http://apigateway.amazonaws.com|apigateway.amazonaws.com>",
    source_arn=deployment.execution_arn.apply(lambda arn: arn + "*/*"),
)

#########################################################################
# Create an HTTP API and attach the lambda function to it
##    /{proxy+} - passes all requests through to the lambda function
##
#########################################################################

http_endpoint = aws.apigatewayv2.Api("http-api-pulumi-example",
    protocol_type="HTTP"
)

http_lambda_backend = aws.apigatewayv2.Integration("example",
    api_id=http_endpoint.id,
    integration_type="AWS_PROXY",
    connection_type="INTERNET",
    description="Lambda example",
    integration_method="POST",
    integration_uri=lambda_func.arn,
    passthrough_behavior="WHEN_NO_MATCH"
)

url = http_lambda_backend.integration_uri

http_route = aws.apigatewayv2.Route("example-route",
    api_id=http_endpoint.id,
    route_key="ANY /{proxy+}",
    target=http_lambda_backend.id.apply(lambda targetUrl: "integrations/" + targetUrl)
)

http_stage = aws.apigatewayv2.Stage("example-stage",
    api_id=http_endpoint.id,
    route_settings= [
        {
            "route_key": http_route.route_key,
            "throttling_burst_limit": 1,
            "throttling_rate_limit": 0.5,
        }
    ],
    auto_deploy=True
)

# Give permissions from API Gateway to invoke the Lambda
http_invoke_permission = aws.lambda_.Permission("api-http-lambda-permission",
    action="lambda:invokeFunction",
    function=lambda_func.name,
    principal="<http://apigateway.amazonaws.com|apigateway.amazonaws.com>",
    source_arn=http_endpoint.execution_arn.apply(lambda arn: arn + "*/*"),
)

# Export the https endpoint of the running Rest API
pulumi.export("apigateway-rest-endpoint", deployment.invoke_url.apply(lambda url: url + custom_stage_name + '/{proxy+}'))
# See "Outputs" for (Inputs and Outputs)[<https://www.pulumi.com/docs/intro/concepts/inputs-outputs/>] the usage of the pulumi.Output.all function to do string concatenation
pulumi.export("apigatewayv2-http-endpoint", pulumi.Output.all(http_endpoint.api_endpoint, http_stage.name).apply(lambda values: values[0] + '/' + values[1] + '/'))

cat iam.py
# Copyright 2016-2018, Pulumi Corporation.  All rights reserved.

from pulumi_aws import iam

lambda_role = iam.Role('lambdaRole',
    assume_role_policy="""{
        "Version": "2012-10-17",
        "Statement": [
            {
                "Action": "sts:AssumeRole",
                "Principal": {
                    "Service": "<http://lambda.amazonaws.com|lambda.amazonaws.com>"
                },
                "Effect": "Allow",
                "Sid": ""
            }
        ]
    }"""
)

lambda_role_policy = iam.RolePolicy('lambdaRolePolicy',
    role=lambda_role.id,
    policy="""{
        "Version": "2012-10-17",
        "Statement": [{
            "Effect": "Allow",
            "Action": [
                "logs:CreateLogGroup",
                "logs:CreateLogStream",
                "logs:PutLogEvents"
            ],
            "Resource": "arn:aws:logs:*:*:*"
        }]
    }"""
)

Any one has idea?