Is it possible to transfer stacks to another Pulumi account?

I have searched for a solution to this but getting nowhere. Can someone please advise how to build a docker image in Pulumi so that it doesn't push a new one to the registry when there were no changes. In my case, that happens on each

pulumi up

which then also triggers a kubernetes deployment. All highly inefficient. Here's how I build:

//context "../../../src/AppABC"
        var imageName = Output.Format($"{_registryServer}/{imageBaseName}");
        var image = new Image($"{appName}-image", new ImageArgs
        {
            Build = new DockerBuild { Context = context },
            ImageName = imageName,
            Registry = new ImageRegistry
            {
                Server = _registryServer,
                Username = _registryUsername,
                Password = _registryPassword
            },
        });

Is there any straight forward way to differentiate between Pulumi stack create and update? Usecase : I want to apply some condition while stack update only (not for stack create). I can achieve the same by set some variable in stack output and check for existence. But just wanted to know any relevant flag from Pulumi end?

Hey folks, I've been trying to get in touch about setting up an Enterprise plan before our free trial expires (just 3 days left now) but I haven't had a response from the contact form. Can anyone point me in the direction of a sales/account contact I can speak to?

Is there a way [in typescript sdk] to get the current project working directory? process.cwd() is not it when passing a pre-built pulumi entry (ie. to avoid using pulumi's typescript versioning and compiler)

We're using

pulumi config set

in a CI/CD pipeline to update the tag of the Docker image. The tag format is the build number we're using -

YYYYMMDD.r

where

r

is the build iteration in that day - for example -

20220117.1

The problem is that since a few days ago pulumi CLI started saving the value as

2.02201171e+07

Any idea what to do with this? 😄

I’ve been working on deploying an app using GitLab as CI/CD and using SSM parameters for storing config variables but have been getting this error:

Error Invoke of 'aws:ssm/getParameter:getParameter' failed: rpc error: code = Unknown desc = invocation of aws:ssm/getParameter:getParameter returned an error: invoking aws:ssm/getParameter:getParameter: Error describing SSM parameter: ParameterNotFound:status code: 400
error: update failed

I’ve verified the parameters, IAM permissions and values of the parameters and everything seems to be fine. It doesn’t give any parameter to check in specific where the error log isn’t being helpful. Any idea on how this can be resolved?

Can anyone confirm whether or not there's a known issue with being able to login to https://app.pulumi.com with GitHub? I've tried multiple browsers on desktop and mobile and it seems like I always get 500s after the exchange has occurred and I get redirected back to app.pulumi.com with the github-callback with the auth code.

Does anyone know how to create a custom domain binding using the azure native api? I cannot find a detailed documentation on that within the azure native sdk.

Good morning, I am having a hard time passing my newly built subnet ids into my EKS cluster For example here is my subnet creation ( I actually create several of them in a loop)

privateSubnet, err := ec2.NewSubnet(ctx, fmt.Sprintf("eks-subnet-private-%d", i), &ec2.SubnetArgs{
                VpcId:               vpc.ID(),
                CidrBlock:           pulumi.String(fmt.Sprintf("%s.1%d.0/24", netWork, i)),
                AvailabilityZone:    pulumi.String(zone),
                MapPublicIpOnLaunch: pulumi.Bool(true),
                Tags:                GetTags(ctx, fmt.Sprintf("eks-%s-subnet-private-%d", environment, i)),
            })
            if err != nil {
                return err
            }

however i haven't quite mastered what should be passed into my EKS. I was assuming a list of private subnets retrieved by using the Apply, but I can't quite put together what that should look like. for example

eksCluster, err := eks.NewCluster(ctx, "eks-cluster", &eks.ClusterArgs{
    RoleArn: pulumi.StringInput(eksRole.Arn),
    VpcConfig: &eks.ClusterVpcConfigArgs{
        PublicAccessCidrs: pulumi.StringArray{
            pulumi.String("0.0.0.0/0"),
        },
        SecurityGroupIds: pulumi.StringArray{
            clusterSg.ID().ToStringOutput(),
        },
        SubnetIds: privateSubnets, << here is my issue
    },
})
if err != nil {
    return err
}

Any help most welcome! Thank you

Is it possible to run a lambda as part of a deployment? So I could say something to effect of this psuedo resource:

Service(..., dependsOn: migrationLambdaRun)

Edit: Found the command package 🙂

I'm new to Pulumi and trying to import an Elastic deployment and getting multiple strange errors all similar to this and not quite sure what they mean. Anyone have any ideas on what is going on? And most importantly, what's the best way to debug issues like this?

ec:index:Deployment (x):
    error: ec:index/deployment:Deployment resource 'x' has a problem: Value for unconfigurable attribute: Can't configure a value for "elasticsearch.0.topology.0.node_roles": its value will be decided automatically based on the result of applying this configuration.. Examine values at 'Deployment.Elasticsearch.Topology[0].NodeRoles'.
    error: ec:index/deployment:Deployment resource 'x' has a problem: Value for unconfigurable attribute: Can't configure a value for "elasticsearch.0.topology.0.instance_configuration_id": its value will be decided automatically based on the result of applying this configuration.. Examine values at 'Deployment.Elasticsearch.Topology[0].Instanc
eConfigurationId'.
    error: ec:index/deployment:Deployment resource 'x' has a problem: Value for unconfigurable attribute: Can't configure a value for "elasticsearch.0.topology.0.autoscaling.0.policy_override_json": its value will be decided automatically based on the result of applying this configuration.. Examine values at 'Deployment.Elasticsearch.Topology[0
].Autoscaling[0].MaxSize'.
    error: ec:index/deployment:Deployment resource 'x' has a problem: Value for unconfigurable attribute: Can't configure a value for "elasticsearch.0.topology.0.config": its value will be decided automatically based on the result of applying this configuration.. Examine values at 'Deployment.Elasticsearch.Topology[0].Config'.

Hello again, I'm trying to import some aws routes into Pulumi. I'm using a command like

pulumi import aws:ec2/route:Route mon2bdefa rtb-0173c706be3_10.3.0.0/16

But it results in:

Previewing import (infra-top):
     Type                 Name             Plan       Info
     pulumi:pulumi:Stack  infra-infra-top             1 error
 =   └─ aws:ec2:Route     mon2bdefa        import     11 errors

Diagnostics:
  pulumi:pulumi:Stack (infra-infra-top):
    error: preview failed

  aws:ec2:Route (mon2bdefa):
    error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "egress_only_gateway_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.EgressOnlyGatewayId'.
    error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "gateway_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.GatewayId'.
    error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "vpc_endpoint_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.VpcEndpointId'.
    error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "vpc_peering_connection_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.VpcPeeringConnectionId'.
    error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "carrier_gateway_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.CarrierGatewayId'.
    error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "local_gateway_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.LocalGatewayId'.
    error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "nat_gateway_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.NatGatewayId'.
    error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "network_interface_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.NetworkInterfaceId'.
    error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "transit_gateway_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.TransitGatewayId'.
    error: aws:ec2/route:Route resource 'mon2bdefa' has a problem: Invalid combination of arguments: "instance_id": one of `carrier_gateway_id,egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id` must be specified. Examine values at 'Route.InstanceId'.
    error: Preview failed: one or more inputs failed to validate

Browsing google for the error leads me to a number of threads talking about legacy Terraform v0.12 such as https://stackoverflow.com/questions/69760888/terraform-inappropriate-value-for-attribute-route Is this a bug? Should I report it to the aws Classic package maintainers on their github or am I doing something wrong?

I am trying to login into pulumi using gcp. it outputs the following error: stderr: error: PULUMI_ACCESS_TOKEN must be set for login during non-interactive CLI sessions. Please let me know if there is any thread on it.

Does pulumi-awsx support python language?

Or is there a best practice for python for aws?

Has the github action repo changed today?

What’s the easiest (lowest friction) alternative to a dynamic provider for Go? I have an API I need to work with that does not have a Pulumi package, and I’d prefer to avoid needing to define a whole package for it just to make some progress.

Based on the docs I’ve seen so far, it looks as if the Docker provider does not have the ability to manage Docker contexts. Does that sound correct?

Hello, I’m trying to spin up a confluent cloud cluster in aws. I can create it in gcp successfully, but when trying aws I get pulumi up error “provider received rpc error”… “* clusters: Oops, something went wrong”. More details in thread. Can anybody suggest how to get to the bottom of this?

Hi what’s the best practice for multiple people working on the same dev stack? Right now our dev stack sets up multiple docker containers locally (with Pulumi generated names) and every time someone’s computer restarts, the next

pulumi up

fails with an error

container XXX cannot be deleted because it cannot be found

(this is not the exact error message) because someone else did

pulumi up

on the dev stack and the container names no longer match.

Hi. Is there any way to export Pulumi to ARM templates?

Hello everyone, greetings! We are trying to adopt Pulumi as an IaC tool to provision resources on Azure platform. I've rather run into a chicken-egg problem when provisioning a `DataBricks Workspace`using the `azure-native`provider with

cmk

. From the docu, I understand that I first need to create the `databricks-workspace`with `prepare_encryption`set to

true

. Once it is created, I need enable

encryption

by providing the key, keyvault to the same resource again. That's something I need to do manually, and do two runs of

pulumi up

. We are using

python

. What's the ideal and better way approach this? Any hints?

quick question for the c# folks. I'm marking my class property with an

[Output]

attribute but noticed in some cases it saves it as a secret but also as plain text.

In Azure Classic you have this KeyVault Uri but I can´t find one word/example what to replace it with in Azure Native

Output.Format($"@Microsoft.KeyVault(SecretUri={KeyVault.VaultUri}secrets/{connectionStringSecret.Name}/{connectionStringSecret.Version}");

I guess you would do it like this? But I get error (

Cannot implicitly convert type 'Pulumi.Output<string>' to 'string'

) on setting the ResourceGroupName and VaultName... how do I solve that?

Has anyone had any luck using pulumi view-trace? Wondering if my command isn't complete enough. The output doesn't appear to be that useful (not used appdash before though) with loads of generic

api:*

spans. I'm ideally looking for which [AWS] resource types is pulumi spending so much time in so I can optimise?

Looking for documentation / guide to migrate a project from a personal user organization to a paid organization, very ideally the deployment under the new organization would not require tearing everything down and rebuilding it.

When was

pulumi/action-install-pulumi-cli

officially deprecated in favor of

pulumi/setup-pulumi

for GitHub Actions? Is there a public notice for this somewhere?

If I need to connect to something like RDS (using the Postgres provider) via an SSH tunnel, two questions: 1. Is there a way to set up the SSH tunnel in the core Pulumi program, as opposed to needing to do it outside (e.g. via a wrapper script or automation API)? Basically, just using

pulumi up

should ideally work. 2. If the SSH tunnel provisions a dynamic local port (e.g. to handle several concurrent tunnels being on the machine), is this going to mess up the provider as the port changes every time?