Hi folks, I am trying to vertically scale a set of readers and writers for a few AWS RDS Aurora clusters (where each cluster has 1 writer and multiple readers). However I would like to sequence the vertical scaling within each cluster such that only 1 instance (or at most a small number of the instances) gets modified at a time. I understand that setting the parallelism level of Pulumi to 1 will achieve this, but I would prefer to modify all the clusters in parallel. If all the resources are within one stack is this approach possible with, say, a Dynamic Resource wrapping the AWS SDK functions to modify the DB instances, or would it be possible to perform this serial execution within a ComponentResource using some approach which blocks on each Resource object until it is done? I would prefer to not use a Dynamic Resource because my limited reading on them suggests that you do not use the Pulumi providers so I'd like to avoid that.

Hello, I’m trying to create an integration to an existing aws websockets gateway route unsuccessfully.

error creating API Gateway v2 route: ConflictException: Route with key $connect already exists for this API

The problem is when i create the

aws.apigatewayv2.Api

resource, The $connect route creates automatically. The only way to create an integration request to a route, is to create the

aws.apigatewayv2.Route

resource in pulumi, and set the integration resource in it. But again, i can’t create the route, because it is already exist.

const exampleApi = new aws.apigatewayv2.Api("exampleApi", {protocolType: "WEBSOCKET"});
const exampleIntegration = new aws.apigatewayv2.Integration("exampleIntegration", {
    apiId: exampleApi.id,
    integrationType: "HTTP_PROXY",
    integrationMethod: "ANY",
    integrationUri: "<https://example.com/{proxy}>",
});
const exampleRoute = new aws.apigatewayv2.Route("exampleRoute", {
    apiId: exampleApi.id,
    routeKey: "$connect",
    target: pulumi.interpolate`integrations/${exampleIntegration.id}`,
});

me and @purple-answer-54279 looking for answers for a long time without any feedback! last time @great-queen-39697 managed to help us. How can we solve it?

is there a way to parse the options for pulumi preview in github actions? I would like to parse a configuration file to the Pulumi review command

Hey all, how do you do slack alerts when deploying? Using a Pulumi package, or your language's equivalent of making a simple POST request? (Some here might do it from elsewhere in CI/CD, but this is specifically a question about doing it from Pulumi)

Hey everyone - do we know if Node 16 is supported?

Hello, I need some help. Im getting this error with Github actions:

getting credentials: exec plugin is configured to use API version <http://client.authentication.k8s.io/v1beta1|client.authentication.k8s.io/v1beta1>, plugin returned version <http://client.authentication.k8s.io/v1alpha1|client.authentication.k8s.io/v1alpha1>

Any walkaround of how to solve this ?

Hi everyone. What would be the Pulumi way of referencing subresources when creating a resource? I am trying to create an application gateway in Azure and I see that all the subresources are referenced explicitly in the examples, something I really need to avoid because their names should be dynamic based on environment and other parameters. Take the following example where I am adding subscriptionId and resourceGroup.name in the definition. I need to do the same with the application gateway name (appgw), frontend IP (appgwfip) and frontend port (appgwfp80), but so far I can only do that by referencing them explicitly as they are being created as part of the same resource:

{
            frontendIPConfiguration: {
                id: pulumi.all([subscriptionId, resourceGroup.name])
                    .apply(([subscription, resourceGroup]) => `/subscriptions/${subscription}/resourceGroups/${resourceGroup}/providers/Microsoft.Network/applicationGateways/appgw/frontendIPConfigurations/appgwfip`)
            },
            frontendPort: {
                id: pulumi.all([subscriptionId, resourceGroup.name])
                    .apply(([subscription, resourceGroup]) => `/subscriptions/${subscription}/resourceGroups/${resourceGroup}/providers/Microsoft.Network/applicationGateways/appgw/frontendPorts/appgwfp80`)
            },
            name: `appgwhttplistener-${environmentLabel}`,
            protocol: "Http",
        },

I am trying to pass a secret to a container's task definition using the secrets property. It is unhappy with a

Secret

resource from

@pulumi/aws/secretsmanager/secret

and seems to expect one from

@pulumi/aws/ecs/container

according to the error message in my editor (attached). ---- The problem I'm having is that I cant find this resource anywhere in docs or code. Any ideas?

I have a very frustrating error that occurs only when I run Pulumi Up. The Review shows not problems. It occurs when I'm trying to create a WebApp Slot in Azure using DotNet Pulumi. Any chance that someone has see this?

hey pulumi team, i was wondering if there are methods on resources for granting permissions, similar to this kind of interface: https://docs.aws.amazon.com/cdk/api/v1/docs/@aws-cdk_aws-s3.Bucket.html#grantwbrputidentity-objectskeypattern it would be very helpful to allow for resource constructs to grant permission to other constructs, instead of having to provision our own policies and sticking it into roles that we then add as resource parameters I haven't had the chance to explore every corner of the docs, but if there is any method for doing this already i'd love to know!

Hi everyone, am I the only one getting a 404 on this link https://www.pulumi.com/registry/packages/gcp/api-docs/serviceaccount/

Hello! Was wondering if anyone has run into this issue using EKS

Kubeconfig user entry is using deprecated API version <http://client.authentication.k8s.io/v1alpha1|client.authentication.k8s.io/v1alpha1>. Run 'aws eks update-kubeconfig' to update.
error: exec plugin: invalid apiVersion "<http://client.authentication.k8s.io/v1alpha1|client.authentication.k8s.io/v1alpha1>"
 
    error: update failed

I was attempting to locate my kubeconfig but theres no config file or directory in

~./kube

so now I'm stuck

Hello… does anyone know regarding case below. I want to run resource based on that stack, but I just want to write in one repo. So I only declare the import module inside the condition. are there any docs/blog/vlog about this?, Thank you.

if (stackName === "development") {
    import "vpc-development"
} else if (stackName === "staging") {
    import vpc-staging
}

I have this simple automation code :

stack = auto.create_or_select_stack(stack_name="core-redis-relay-5" , program=common.create_relay , work_dir="buildlib/infra-python")
stack.up(on_output=print)

in

create_relay

I do pulumi.log / print but I can't see their output ? How can I select the log level with automation ? how can I see my prints ?

What is a proper/intended way to learn about

CodePathOptions

it took me 3 hours and various github issues to land on that page? https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/runtime/closure/#CodePathOptions

ok, am I only one that pulumi.com has lot of 404 for documentation? ex: https://www.pulumi.com/registry/packages/gcp/api-docs/serviceaccount/iampolicy/ this is indexed in google search and pulumi.com search

For CDK support on Pulumi: is there / will there be a way to use Pulumi constructs with CDK constructs and vice versa? not just solely using CDK within pulumi scripts but creating a CDK resource and then using this resource as a parameter to a Pulumi resource? For example,

taskdef = new cdk.ecs.FargateTaskDefinition(...)
ecs = new awsx.ecs.FargateService({
    taskDefinition: taskdef,
    ...
})

Hey all, quick question on the new GCP database Alloy DB just launched at GCP IO 2022. Are we able to deploy and manage Alloy instances yet through Pulumi?

Hey, folks! I see that there are a bunch of theme chats like #aws #gcp but there’s no Oracle Cloud (OCI) channel/chat. Let’s create one!

I am unable to install a pulumi provider package (pulumi-eks). This could be due to the fact I’m using a mac M1 and related to the 403 HTTP error fetching plugin. I wondering if other M1 users had found similar issues? The error message is not too helpful:

Running setup.py install for pulumi-eks ... error
ERROR: Command errored out with exit status 1: 
[...]
[resource plugin eks-0.39.0] installing
   
Downloading plugin: 0 B / 682.52 KiB [---------------------------------]   0.00%
Downloading plugin: 682.52 KiB / 682.52 KiB [=======================] 100.00% 0s
env: node: No such file or directory
error: installing [resource plugin eks-0.39.0] from : installing plugin dependencies: exit status 127

So

pulumi-eks

appears to be the failing point on new installations for the

v1alpha1

deprecation issue. I see there's a PR that actually fixes the problem I had yesterday https://github.com/pulumi/pulumi-eks/pull/701/commits I'm pretty new to Pulumi but was wondering what a PR merge schedule looks like for these packages. I'm currently building the package myself and installing it for now but would like to have the officially built package installed instead. I hope this message doesn't come off as rude cause I know everyone's busy 😅 but I'm so far enjoying the experience with Pulumi 🙂

Pulumi CLI has a preview option for the destroy command — question: how can we do this (preview of destroy) using the automation-api?

Hey folks! I have a full CRUD API Schema I would like to put in a new provider. I am aware of all the boilerplates, but they miss documentation for golang newcomers. I don't want to write all the API Calls for all resources, I want it to take the schema and do an generic fetch with the defined properties as parameters and the resource name as path. Any easy to start tutorial how to achieve this, you can share? Everything I found so far is either not well explained or not showing how to handle many resources with an API. (In TS I would know how to do it, but Providers have to be written in golang). There has to be a way to do it without writing thousands LOCs. 😕

Hey Team! How can we create a GCP project through pulumi with the same PROJECT_ID on GCP different accounts?

Hi, this doc page doesn’t present the languages like the other ones, but one after the other: https://www.pulumi.com/registry/packages/aws/api-docs/cloudwatch/eventtarget/

Hey Team! How can we create a GCP project through pulumi with the same PROJECT_ID on GCP different accounts? It is really important for me to know this since the resources I am creating thru pulumi IAC are utilized in the CICD pipeline, therefore I really need to have fixed Project_ID to avoid any manual changes and smooth CICD deployment.

Hey all! How can one use the pulumi outputs to build a dockerfile that uses that output as an environment variable? Similar to this question in SO: https://stackoverflow.com/questions/61194555/how-to-pass-environment-variable-to-dockerfile-through-pulumi

Hey All !! I have created a new project and a stack called test with the latest pulumi versions . It has an aws provider as default_5_4_0 . There is another stack called dev(existed before) which i am using as part of the newly created project . This stack has the aws provider as default_2.6.0. This was created earlier . When i try to change the stack from test to dev and try pulumi up/preview get the following error attached below . Also i cannot install the previous version of the aws provider 2_6_0. Gives me a 403 forbidden error. How do you deal with this?