I was going through this pulumi tutorial (https://www.pulumi.com/learn/pulumi-fundamentals/configure-and-provision/), but it's failing with error(container exit...) . After inspecting the image built, I found that it is taking the "Architecture": "arm64" for building image, and I am using Ubuntu amd64. I am sure it's the reason why it's failing. But not sure why it is taking the arm64 eventhough the Dockerfile mentioned "FROM mongo:focal"? Any idea??

Guys, I'm getting started with Pulumi using Docker and I'm getting an error for the volume path because I'm using a relative path instead of an absolute path. How do I not hardcode the path?

./redis/redis.conf

is within the Pulumi project. I tried using `HostPath = $"{Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location)}\redis\redis.conf",`but it exceeds the max path length of 255 and doesn't reach out that part.

docker:index:Container (RedisContainer):

error: docker:index/container:Container resource 'RedisContainer' has a problem: './redis/redis.conf' must be an absolute path: './redis/redis.conf' must be an absolute path. Examine values at 'Container.Volumes'.

return await Deployment.RunAsync(() =>
{
    var stackName = Deployment.Instance.StackName;
    const string redisHost = "redis";

    // Get configuration
    var config = new Pulumi.Config();
    var redisPort = config.RequireInt32("redisPort");

    // Create network
    var network = new Network("network", new NetworkArgs
    {
        Name = $"services-{stackName}"
    });

    // Find the latest redis image
    var redisImage = new RemoteImage("RedisImage", new RemoteImageArgs
    {
        Name = "redis:alpine"
    });

    // Start a container
    var redisContainer = new Container("RedisContainer", new ContainerArgs
    {
        Name = $"redis-{stackName}",
        Image = redisImage.Latest,
        Ports = new InputList<ContainerPortArgs>
        {
            new ContainerPortArgs
            {
                Internal = redisPort,
                External = redisPort
            }
        },
        Command = new InputList<string>
        {
            "redis-server /usr/local/etc/redis/redis.conf --requirepass mypassword"
        },
        Volumes = new InputList<ContainerVolumeArgs>
        {
            new ContainerVolumeArgs
            {
                HostPath = "./redis/redis.conf",
                ContainerPath = "/usr/local/etc/redis/redis.conf"
            }
        },
        NetworksAdvanced = new InputList<ContainerNetworksAdvancedArgs>
        {
            new ContainerNetworksAdvancedArgs
            {
                Name = network.Name,
                Aliases = new[]
                {
                    redisHost
                }
            }
        },
    });

    // Export
    return new Dictionary<string, object?>
    {
        ["redisContainer"] = redisContainer.Name
    };
});

Hey everyone! Been using Pulumi in production for a few months now and it works great! What's the most reliable and robust way to determine which resources were updated via the Pulumi GitHub action?

To me, this looks like a bug:

Hello! Can you please help with this PR https://github.com/pulumi/pulumi/pull/11467 ? This fix is critical to generate the NodeJS SDK. The issue is described here: https://github.com/pulumi/pulumi/issues/11466

I deleted my stack, but before doing so, I exported the stack using

pulumi stack export...

, and then tried to import it, but getting this error:

error: this command requires a stack, but there are none

Isn't it possible to import stack once deleted?

Hi all, I have a question regarding security group ingress. It can be specified using the ingress argument or using the SecurityGroupRule. The latter has the source_security_group_id argument, which is what I would like to use. Does specifying security_groups under SecurityGroupIngress have the same effect?

does the pulumi site have dark mode because the white is killing my eyes? 😕

Hi all, I have a question about Custom API from the docs. I can not understand why the example needs

spin_venv()

function to prepare a virtual environment.

Good morning everyone! I've always been using the

pulumi-base

docker image for my pulumi workloads with my dotnet based pulumi programs. From and including the image tagged

3.47.0

, i'm getting a

error: could not find `dotnet` on the $PATH: exec: "dotnet": executable file not found in $PATH
error: failed to load language plugin dotnet: could not read plugin [/pulumi/bin/pulumi-language-dotnet] stdout: EOF

Whereas with the image tagged

3.46.0

, i'm not seeing it. If I use

pulumi-dotnet

it does work, my curiosity is in why the

pulumi-base

worked previously and stopped working.

Is pulumi so stupid, that if there is an error in the code, it goes ahead and just deletes stuff, without saying do you actually want to do this first? Shouldnt it actually ask you, this is preview, I am going to do a bunch of things, continue on your own risk?

When writing a ComponentResource, what's the right way to name the type? In the examples I see

pkg:index:MyComponent

. Should I replace

pkg

with my package name and

index

with a module name?

Hi All, I have a question on backend migration: • Currently, I'm using Pulumi Service backend to store state. Now, we are planning to migrate the state to our managed S3 bucket for some reasons. • By referencing the section [Migrating Between State Backends] in https://www.pulumi.com/docs/intro/concepts/state/, the state can be exported and imported to our S3 bucket successfully in my test. • However, the original state seems to be retained in Pulumi Service backend as well. • Is it possible to remove the original state stored in Pulumi Service backend? If yes, how to remove it safely? Thanks!!

We have a case where I need to we have resources shared across different subscriptions (or accounts). In this specific case I need to update the firewall in one subscription and telling it to accept data from a vnet in a different subscription. What would I do? I cannot find any obvious documentation regarding this (other than manually creating a provider, but I just need to use a different subscription).

Anyone is using the ingress (for kubernetes) package ? I'm wondering why I meet the current issue : When I need to build an image for a service, my ingress gets a "connexion refused" error, and fails to create. I need to do a second

pulumi up

when everything else is ready to have it working. I'm using it exactly like in the examples. Any idea ? :s. All I saw is that if i'm pulling an image and not building it, everythings seems to work fine...

Hey all, hope everyone doing great. I wander if there is Pulumi apis which support Tags management. Basically api for this command:

pulumi stack tag set

hey everyone, do you know if is it possible to work with micro-stacks using a self-managed backend?

hi again, how do I find the versions of terraform providers embedded inside pulumi, and can I upgrade them manually?

Hi again, can someone please help with the following: A. I created a console app that basically presents 2 folders : Classic & Native. Some resources are available in both but some are only available in classic or native i.e CosmosDB only exists in Classic (right?). You can't go on full native or full classic, its a mixture. Is that assumption correct? B. I have a basic CI/CD and it integrates Pulumi (Preview and Up). I have managed to deploy the desired state in dev environment. I need to take this further and next deploy to Test and QA. So, same resources but different names i.e dev-uk-orders-rg, test-uk-orders-rg. Do I control that via stacks? i.e ${stack-name} as a variable in my variables list so for dev environment we have dev-kyc-slack and for test we "tell" it to use the test-kyc-stack? The difference between dev-kyc-stack and test-kyc-stack is just name prefix (for now). Is that approach correct or is there a better way? (edited)

Hey guys what's the status of Dynamic Provider support for Golang? Or building a native provider https://github.com/pulumi/pulumi-provider-boilerplate is the way to go?

has anybody tried using this Terraform provider for Terraform to access Pulumi outputs? any issues? https://registry.terraform.io/providers/transcend-io/pulumi/latest

Hi All 🙂 Do you know what would be the reason that I’m getting following error when I hit the endpoint of

aws.lambda.CallbackFunction

{
  "errorType": "Error",
  "errorMessage": "Cannot find module 'tslib'\nRequire stack:\n- /var/task/__index.js\n- /var/runtime/index.mjs",
  "code": "MODULE_NOT_FOUND",
  "requireStack": [
    "/var/task/__index.js",
    "/var/runtime/index.mjs"
  ],
  "stack": [
    "Error: Cannot find module 'tslib'",
    "Require stack:",
    "- /var/task/__index.js",
    "- /var/runtime/index.mjs",
    "    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)",
    "    at Function.Module._load (node:internal/modules/cjs/loader:778:27)",
    "    at Module.require (node:internal/modules/cjs/loader:1005:19)",
    "    at require (node:internal/modules/cjs/helpers:102:18)",
    "    at /var/task/__index.js:5:21",
    "    at Runtime.__f0 [as handler] (/var/task/__index.js:14:6)",
    "    at Runtime.handleOnceNonStreaming (file:///var/runtime/index.mjs:1089:29)"
  ]
}

has anyone tried sending pulumi traces to datadog apm ?

Hi team, glad to be here. I am new to Pulumi. And wanna try pulumi-pagerduty. Is there any examples to get started?

Is there anyway in which we can write internal pulumi packages and that other components can consume, and are listed on some internal registry or something. Even use case is not to have registry but directly referring to pulumi package via git or something.

👋🏻 Hey All 🙂 Another question regarding lambda + apigateway : I’m trying this crosswalk https://www.pulumi.com/docs/guides/crosswalk/aws/api-gateway/ I’m using the code as it is with exactly as it is :

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

// Create a Lambda Function
const helloHandler = new aws.lambda.CallbackFunction("hello-handler", {
    callback: async (ev, ctx) => {
        return {
            statusCode: 200,
            body: "Hello, API Gateway!",
        };
    },
});

// Define an endpoint that invokes a lambda to handle requests
const api = new apigateway.RestAPI("api", {
    routes: [
        {
            path: "/",
            method: "GET",
            eventHandler: helloHandler,
        },
    ],
});

export const url = api.url;

But unfortunately I’m stucked with this error :

error: update failed

  aws:apigateway:RestApi (api):
    error: 1 error occurred:
        * creating urn:pulumi:dev::meeting-integrations::aws-apigateway:index:RestAPI$aws:apigateway/restApi:RestApi::api: 1 error occurred:
        * error creating API Gateway specification: BadRequestException: Errors found during import:
        Unable to put integration on 'GET' for resource at path '/': Invalid ARN specified in the request

Do you have any knowledge about this issue?

does anyone know what cause of this issue

Has anyone developed pulumi native provider? Looks like https://github.com/pulumi/pulumi-provider-boilerplate repository is incomplete. I'm trying to setup a native provider repository for myself, would really appreciate any support to get it working.